On Mon, Jun 1, 2009 at 10:59 AM, Suren <[email protected]> wrote: > but I want to confirm is there any other ways of doing > it. So at the end, its not possible..hmm. > > So now what I am trying to do is, Storing the keycolumns of the rows > initially sent to client in an array, and I am initiating the request > from the client now, and fetching the same values from the DB and > comapring with the existing values. If there is a difference then > sending that to client, else leave that row as such.. > > Tell me if anyother way of doing it, or is there any disadvantages of > doing it?
I use auto_increment primery keys, so new rows are greater than the last send to client. Each minute the client polls the server /example/path/new_objects?from=2353 (beware IE caching). JQuery in client, and json encoding in the server (search djangosnippets.com) makes this a joke, no more than a few hours to implement. If you want also notify modifications (my model is inmutable) you should store some kind of version indicator. If you need near real-time updates investigate comet. I have no experience with it. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
