As far as i remember JimD rewrote ns_http using new tasks API, but other
than that i do not know where/how tasks API is used.
Tasks API is good, i agree it is more generic and Tcl interface can be
built around it so instead of using Tcl event loop it will be possible
to use tasks. with Tcl main loop you need to spawn separate threads if
you need multiple tasks to be queued from different threads/places.
Zoran Vasiljevic wrote:
Am 04.01.2006 um 16:10 schrieb Vlad Seryakov:
I believe poll can be used on any file descriptor, not only sockets.
It is generic socket/fds callback infrastructure, it is very similar
to socket callbacks we already have in sockcallback.c.
Does not make sense to have both, they duplicating each other
Hm... on the first glance, yes... I think the benefit of
"task" interaface is that it's more genral in terms of
the API. Actually, one could re-write the latter with the
former, as I can see.
The sockcallback exports just two/three calls:
Ns_SockCallback
Ns_SockCancelCallback
Ns_SockCancelCallbackEx
whereas the task is much more elaborate.
The question is who would benefit from task interface?
Are there any immediate ideas?
For what they (AS) wrote it for?
What can it do what Tcl event loop can't?
Zoran
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
naviserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
--
Vlad Seryakov
571 262-8608 office
[EMAIL PROTECTED]
http://www.crystalballinc.com/vlad/
