Koen Deforche wrote: > WSocketNotifier is a sore point of Wt... It appears that it is > impossible to implement the current API properly using asio (and we > blame asio, we have filed a bug on it to the asio people but they seem > not to care although they have changed the related API). It would be > possible to implement it using FastCGI but since we have no good > overall solution, we didn't yet.
I'm on the asio list evey now and then -- what bug report are you referring to? > I would recommend to steer away from it, and instantiate your own asio > service with one or more threads, and use the WApplication's update > lock if you want to manipulate widgets as a result of notifications > (you'll probably need a WTimer or server-push to propagate the info > back to the user). I'll look into it. Thanks, Cheers, Rutger ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
