[Catalyst] Handling long-running processes (was Re: Logging is not immediate)

Toby Corkindale toby.corkindale at strategicdata.com.au
Wed Oct 20 00:48:39 GMT 2010

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! :)


More information about the Catalyst mailing list