From: Michael B. <mbe...@mb...> - 2007-07-20 12:43:53
|
Silvio wrote: > > My problem is I can't know what user do: he has a html form in wich edit > > Any tag of dogument. When he submit the form my idea was to update entire > > Document. This is actually a different problem area, although it does explain your current need for whole-document deletions and replacements. It depends on how complex the form is, what kind of changes the user can make to it, and maybe also how many simultaneous users there may be. In one of my applications, the client form has an Ajax event handler that tracks changes to the html DOM and signals them asynchronously to the server, which can shadow them in real time against its own copy of the XML DOM. So the server already knows when the user-visible submit button is clicked which nodes have been changed client-side and in what way, and can make a judgement based on that knowledge whether to do XUpdates or a complete delete and re-store. But I guess that is only feasible in quite specialised cases such as this one (a handful of users making changes governed by strong constraints to small but highly-structured documents on a server on the same Gigabit LAN). Michael Beddow |