Hey, 2008/9/6 <[EMAIL PROTECTED]>: > Has anyone used this along with triggerUpdate() on FCGI deployment? > > On my setup this works fine when launching with embedded HTTP server, > but with fcgi+apache it fails. > Application launches but any event leads to application reload...
Do you get any errors in the console? You should make sure you have Wt's resources/ directory deployed, since enableUpdates() requires resources/orbited.js. If so, then it should work to some extent: most fastCGI extensions (such as mod_fastcgi for apache) will consider an idle period on a request as a failure (for mod_fastcgi, the default is 30 seconds). However, server push works by using such a long request. You can get around this by using a really large timeout. Also, most fastcgi implementations will not multiplex data for multiple requests over the same connection. Therefore, short requests can get temporarily queued after the long request, until an internal timeout is hit to spawn a new FastCGI process (which is fine, unless you only want one process as for example the simplechat example requires to avoid IPC). I have not that much experience with the other fastcgi implementation for apache (mod_fcgid) and fastcgi implementations for other web servers... They may behave better... Note that server-side updates are not yet reliable, and much has to do with this long connection not being well supported by also intermediate (reverse) proxies. Workarounds are known but not yet implemented... Regards, koen ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ witty-interest mailing list witty-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/witty-interest
