Re: Socket access (for close)

On Wed, 2 Sep 2009, Neil Gierman wrote:

> My question is, should we have access to the raw socket from our clients, or
> should we implement socket closing inside the library?

The former, I say.

> Since we are required to create the socket outside the library, it makes
> sense to me to also close the socket in our own application, however we
> can't do that without access to the socket.

How did you lose the socket in the first place? You created it, you told
libssh2 about it. Why can't you just keep track of it and close it when
libssh2 is done with it?

-- 
  / daniel.haxx.se
_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel