On 20/10/10 09:19, Chris wrote:
I'm curious to know how other people approach this issue.
Also, what do you think about the polling approach vs a (background)
connection that stays connected waiting for the completion signal?
I've found polling much simpler to implement (and test) as it doesn't
require anything particularly special on either client or server-side.
It means a bit more delay - the polling period - before the user gets
the result, but for our use-case (generating reports and download
files) this hasn't been an issue. I've seen some stuff suggesting that
polling leads to higher server load, but again it hasn't been an issue
in our low-traffic web-apps.
I still haven't played with Comet-style server-push much. Anyone else
using it?
What is support like for either multi-part or partial-update in browsers
like now?
Although HTML5 will clean it all up, since it actually defines some
proper transports. Then we just have to wait for HTML5 support to be
prevalent! :)
-Toby
_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
