Patches item #472822, was opened at 2001-10-19 15:31 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=303152&aid=472822&group_id=3152
Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jeremy Collins (jcollins) Assigned to: Kriston Rehberg (kriston) Summary: tclsock.c patch Initial Comment: This is a simple patch to tclsock.c in ./nsd that causes SockListenCallback to evaluate each new connection in a separate thread. This allows the listening port to continue listening so multiple connections can happen. I am not sure I did this change the most logical way. Hopefully somebody could check it and give me feedback. ---------------------------------------------------------------------- >Comment By: Jeremy Collins (jcollins) Date: 2002-03-24 06:05 Message: Logged In: YES user_id=1031 Its been a while since I wrote this but I am pretty sure that this only affects the ns_sock* Tcl commands. I guess I wasn't very specific about that in the patch description. To give you some history. I wrote a Tcl version of nscp so that I could implement readline type features. The problem I kept having was that I could only make a single connection to the script at a time. This patch fixes the problem by evaluating the script (from ns_sockcallback) in a separate thread. Here is how I was listening on the port: ns_socklistencallback 127.0.0.1 8888 nscp_accept ---------------------------------------------------------------------- Comment By: Kriston Rehberg (kriston) Date: 2002-03-20 16:28 Message: Logged In: YES user_id=16427 Just so I can understand this: This would only affect things in a sockcallback thread, but will *not* affect a communications driver like nssock, nsssl, nsunix, or nsopenssl? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=303152&aid=472822&group_id=3152
