On Jun 4, 7:53 pm, John Mettraux <[email protected]> wrote: > in the context of a "web page", what about having the page refresh itself > intermittently, la Gmail ? > > Or if your users have an up-to-date browser, what about [ab]using websockets > and let the server notify the web page of new workitems ?
Yes, we discussed this, and decided that Comet would probably be a great long-term solution for other situations. It's not appropriate for this situation because we're already doing a page refresh, and if the user sees a new page that doesn't have their changes represented, they might do something drastic like hit their back button. Even if we automatically update the page once their changes go through (fully embracing asynchronicity), it might be too late--they might have already navigated away. In order for it to work well, the user-interaction cycle would have to be completely asynchronous. That is, the form submission, and any and all responses. The degree of change required is way too involved. Until writing Comet apps becomes as easy or easier than writing traditional apps, I suspect we'll continue doing it this way. > Thanks for sharing your experiences. > > It's true that we're all a bit wary of "anticipating the flow", because it > usually means that changing the flow will break the anticipations / > expectations. > > I hope you're having good fun and that ruote helps you in your work. I cannot express in words how awesome ruote is, nor how much it has helped me in my work. It's one of those things I always thought should exist, and am thrilled that not only does it finally exist, but that it's quite nicely executed to boot. Thanks so much for your efforts building it. -Ian > > Cheers, > > -- > John Mettraux -http://jmettraux.wordpress.com -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
