From: Suman Nath (sknath@cs.cmu.edu)
Date: 04/23/03
Hi Ganesh
In the version (stable030203) of IrisNet you are using, SA sends XML paths
and values to update. OAs then construct the necessary XUPDATE commands to
do the update.
However, this does not reflect the true potential of XUPDATE, since OAs
only "replaces" existing values. However, real XUPDATE supports a lot of
other operations like node addition, deletion etc. IrisNet's OAs actually
supports any arbitrary XUPDATe commands, but currently there is no way for
SAs to use that feature.
The new version that I will send to you will allow SAs to send
arbitrary XUPDATE commands to the OAs (thus SAs will have more control
over how to manipulate the data). I will send the code to you soon. In the
mean time, you may like to look at the following links to get an idea
about XUPDATE specification and syntax. Thus when you have our code, you
can write senselets to construct required XUPDATE commands.
1. http://www.xmldatabases.org/projects/XUpdate-UseCases/ : excellent page
with a lot of examples of allmost all possible XUPDATE commands.
2. http://www.xmldb.org/xupdate/ : XUPDATE specification
3. http://www.xindice.org/Resources/XindiceDocumentation.html : xindice
documntation page.
For now, I think the 1st link would be enough for you. The page
gives a lot of example xupdate commands. Your senselet should be able to
construct similar xupdate commands that suit your schema.
Dont worry, I will help you in case you find something alien.
Suman
This archive was generated by hypermail 2.1.5 : 04/23/03 EDT