I combined the last code Dmitry sent with using abort_selector when
anything is added to buffer and there is now an even more stable single
task solution. I'm very satisfied with performance CPU and communication
wise now with this. So I've been moving on now to other areas to get done
for 1.0. I am sure that or a modification of it will be the final in 1.0.
Dmitry in this last update also added the ability to leave open the http
connection for continue write. This open the door for a key fall back
mechanism, the combination of continue writes and ajax event notifications.
Depending on time I may or may not have that in for 1.0. The would take
care of issues related to websockets over unsupported firewalls. It doesn't
per se deal with the issue of non-javascript aware web crawlers. That
though is low priority since a no-script tag can be added to boot html file
for that purpose. The plan to handle non-javascript crawlers, if I end up
doing it, will be to render to a webkit context and then dump the results.
David Botton
> A different solution is to introduce signalling sockets:
>
>
> I mentioned the idea of using and out-of-band signal if he wants to stick
> with one task. Will see.
>
> David Botton
>
>
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Gnoga-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gnoga-list
