behaviour of Unix.shutdown_connection

behaviour of Unix.shutdown_connection

[Alan Schmitt]

If I open a connection with Unix.open_connection, and shut it down
with Unix.shutdown_connection, do I still need to call close_in and
close_out on the two channels ? 

Si j'ouvre une connexion avec Unix.open_connections, et la ferme avec
Unix.shutdown_connection, est-il nécessaire que je ferme les deux
canaux par close_in et close_out ?

Amicalement,

Alan Schmitt

--
The hacker: someone who figured things out and made something cool happen.

[Caml-list] Re: behaviour of Unix.shutdown_connection

[Xavier Leroy]

> If I open a connection with Unix.open_connection, and shut it down
> with Unix.shutdown_connection, do I still need to call close_in and
> close_out on the two channels ? 

Yes.  Basically, shutdown_connection just sends an "end of file"
condition to the program connected to the socket on the other side.
The other program can then finish sending what it has to send, then close
its side of the socket.  On receiving an "end of file" on your side,
your program knows that the data exchange is over and can (and must)
then close the descriptors on its side.

- Xavier Leroy
-------------------
To unsubscribe, mail caml-list-request@inria.fr.  Archives: http://caml.inria.fr

Re: [Caml-list] Re: behaviour of Unix.shutdown_connection

[Daniel de Rauglaudre]

On Thu, Feb 15, 2001 at 03:20:41PM +0100, Damien Doligez wrote:

> So you must close the out_channel that was returned by
> Unix.open_connection, but not the in_channel; and this is true whether
> you called Unix.shutdown_connection or not.
> 
> Warning: I have not tested it.

If you proved it correct, no problem.

-- 
Daniel de RAUGLAUDRE
daniel.de_rauglaudre@inria.fr
http://cristal.inria.fr/~ddr/
-------------------
To unsubscribe, mail caml-list-request@inria.fr.  Archives: http://caml.inria.fr

Re: [Caml-list] Re: behaviour of Unix.shutdown_connection

[Damien Doligez]

>From: Xavier Leroy <Xavier.Leroy@inria.fr>

>Yes.  Basically, shutdown_connection just sends an "end of file"
>condition to the program connected to the socket on the other side.
>The other program can then finish sending what it has to send, then close
>its side of the socket.  On receiving an "end of file" on your side,
>your program knows that the data exchange is over and can (and must)
>then close the descriptors on its side.

There is only one descriptor, and it is shared between the two
channels.  Thus if you close both channels, then the descriptor gets
closed twice.  If it was reopened in-between (for example in a
multithreaded program), then some unrelated part of your program will
have its descriptor closed under its feet.

So you must close the out_channel that was returned by
Unix.open_connection, but not the in_channel; and this is true whether
you called Unix.shutdown_connection or not.


Warning: I have not tested it.

-- Damien
-------------------
To unsubscribe, mail caml-list-request@inria.fr.  Archives: http://caml.inria.fr