Re: [bdbxml] A brief comparison of XmlModify and Xupdate techniques

George Feinberg <[email protected]>
Newsgroups gmane.comp.db.dbxml.general
Message-ID <[email protected]>
XUpdate is a declarative language to specifying update operations.
It is an XML grammar.  This is useful when you have a client-server
architecture and need to specify an update operation, or set of
operations via RPC, for example.

The XmlModify interface in BDB XML is a direct programming API
that allows you to specify similar operations.  It is more useful
when you are programming updates directly.

Consider the XUpdate scenario.  The user must do these steps:
1.  decide what to do (e.g. insert a new node, and modify an  
attribute value)
2.  encode that set of operations in the XUpdate grammar (i.e. write  
an XML
string)
3.  send that string to the implementation of XUpdate.

The implementation then does this:
1.  parse and decode the XUpdate into a sequence of operations
2.  perform the operations

In the BDB XML XmlModify scenario, the sequence is similar, with
some steps removed.  In this scenario, there is no distinction
between the user and the implementation.  The user does this:

1.  decide what to do (e.g. insert a new node, and modify an  
attribute value)
2.  pass those operations to XmlModify and related objects.
3.  execute the update

In effect, the BDB XML API is what an implementation of XUpdate might
use to perform its updates.  It skips the steps where you need to
encode/decode the operations into an XML string.

Regards,

George

>
>
> Hi everyone,
>
> I understand that bdbxml doesn't support Xupdate for updating its  
> data.
>
> I am interesting in having a brief comparisons these two update  
> techniques. (e.g. their strengths and weaknesses)
>
> I will appreciate your input please.
>
> Thanks in advance for your feedback
>
> N Mabanza
>


------------------------------------------
To remove yourself from this list, send an
email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.