Can you remind us the great features of the new Tamino API.

Is incremental update a part of it ?

If yes, how does it behave with Tamino wich doesn’t support Incremental update ?

J-F Declercq
Software AG Belgium
+32-2.777.03.28

Hi Jean-Francois,

no, the new API does not support incremental update or node-level-update. We will support it, as soon as Tamino supports it.

Cheers,
Christian.

If you want to simulate Node level update
then there is only one possible configuration

Use IIS,
Install the node levelupdate dll
Use the node level update methods of the Tamino API 1. Java/OCX etc

Node level update works by reading the document into memeory on the server side doing the update
and writing it back.

regards

Nigel Hutchison

Say, people,

for node level update we pull things out of the database, create a DOM in memory (server-side or client-side), make our changes and put it back into the database.

Does anyone know how exactly an sql system performs an update? Couldn’t it be that they are pulling out the whole row, updating the cells they want to and write back the whole row. They might just do it in a less exposed fashion than we do.

For example, RAM handles updates much the same way: get a whole row (128bit) out of the chip into a special buffer, change bits, write back the whole row, even for a measly bit to change.

Curious,

Andreas

Andreas,

I’m not sure what you want to say with this.

However I think an update in a row of RAM bits, which is moved in a fixed cycle time no matter how long it is and the update of an XML document, which is moved between a datastore and a webserver plugin, including several transformations between string and DOM format and a TCP/IP connections in between are quite two different stories.

A real fast update of parts of a document can only happen within the database server.

Cheers, Christian.