The pattern you've described doesn't sound too awful in practice, but  
if you start updating large chunks of your page at once, consider  
making the server share some of the work with the client. If you've  
already got the whole page there, and all the script, it doesn't make  
sense to (for example) update an entire table or grid when you've just  
deleted a row or re-sorted the contents. If you can get away with  
posting only the new sort order or the delete request to the server,  
and updating the page in the browser when you get a 200 header back  
from the update script, then you can improve your performance quite a  
lot, both for the client and the server.


On Jan 26, 2009, at 9:48 PM, wrote:

> My question is, how sloppy is this?  Or is it a viable implementation?

You received this message because you are subscribed to the Google Groups 
"Prototype &" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to