oops, we put it into closing list which calls release in the driver. please
ignore
Vlad Seryakov wrote:
> Is this intentionally that NsSlsCleanup is called only in SockRelease but not
> in SockClose. For normal connection which
> call NsConnClose, SockRelease is not called and therefore SLS is
Is this intentionally that NsSlsCleanup is called only in SockRelease but not
in SockClose. For normal connection which
call NsConnClose, SockRelease is not called and therefore SLS is never cleanup?
--
Open Source Busin
I did not do anything yet, just running the idea by.
Persistent conns are available right now, our driver supports it, just
need to set keep alive timeout to be long enough and you have TCP
connection for free. The callbacks for cleanup i think should be running
on NsConnClose in the same threa
On Mon, Mar 2, 2009 at 6:31 PM, Vlad Seryakov wrote:
> I am working with persistent connections right now and want to track when the
> socket is closed to cleanup some memory in
> Tcl but it looks like there is no way to call cleanup Tcl proc on socket
> close. I am thinking to extend ns_sls to
I am working with persistent connections right now and want to track when the
socket is closed to cleanup some memory in
Tcl but it looks like there is no way to call cleanup Tcl proc on socket close.
I am thinking to extend ns_sls to attach
Tcl proc to be called at cleanup stage.
Is this right
