[
Lists Home |
Date Index |
Thread Index
]
Robin Berjon wrote:
> Steven J. DeRose wrote:
>
>> How about putting an ID on every changeable node, and then sending
>> something like:
>>
>> <replace target='someID'>
>> ...new XML for that node...
>> </replace>
>
> Yes, that or an XPath should work quite well. It's routinely done in a
> variety of situations. You may wish to look at XUpdate for instance
> (assuming you want to reuse an existing piece of technology).
I just took a look at XUpdate. And it seems to be OK, but I need some
funny callbacks on the client side.
And they are very important for my project. And I did not find them in
XUpdate.
I got my big XML document on the Client side. I can somehow identify
each element and each attribute in my big XML document somehow. So I got
some kind of XML pointer to a specific attribute of a specific element.
The Client API must provide function like this:
install_xml_callback(pointer_to_XML_attribute, pointer_to_callback_function)
Whenever this attribute has changed the callback_function has to be
called with at least the following parameters:
callback_function(pointer_to_XML_attribute,new_value_of_the_attribute)
"has changed" is of course equivalent to has been received from the server.
********
Does anyone know if this works with XUpdate, or does anyone know if
there is any system that can give me these callbacks?
**********
The reason why I need them I that I want to display the XML document (or
rather parts of it) in a graphical user interface. And I need to update
the GUI whenever the XML document changes. Otherwise I would
have to use some polling mechanism, which eats CPU time.
>> Can you be certain that all change requests will be received, and in
>> the order they were sent? If not, the problem gets much messier; but
>> probably you can ensure that somehow.
>
Yes I can. At least I think so if I simply connect Client and server via
a TCP/IP connection.
Cheers Dirk
|
