En Sun, 14 Dec 2008 06:03:26 -0200, greg
escribió:
Gabriel Genellina wrote:
(Pipes don't work the same as sockets, although unix-like systems try
hard to hide the differences...)
BSD-based unixes implement pipes using socketpair(), so
pipes actually *are* sockets (or at least they used to
En Sun, 14 Dec 2008 09:37:38 -0200, Emanuele D'Arrigo
escribió:
On Dec 14, 4:48 am, "Gabriel Genellina"
wrote:
- you have to close server.stdin when you don't have more data to send.
The server will see an end-of-file and knows it has to exit the loop.
Same thing on the client side.
Hi Ga
On Dec 14, 4:48 am, "Gabriel Genellina"
wrote:
> - you have to close server.stdin when you don't have more data to send.
> The server will see an end-of-file and knows it has to exit the loop.
> Same thing on the client side.
Hi Gabriel, thanks for modifying the code to make it work. I've just
tr
Gabriel Genellina wrote:
(Pipes don't work the same as sockets, although unix-like systems try
hard to hide the differences...)
BSD-based unixes implement pipes using socketpair(), so
pipes actually *are* sockets (or at least they used to be,
not sure whether it's still true).
--
Greg
--
htt
En Sat, 13 Dec 2008 18:19:29 -0200, Emanuele D'Arrigo
escribió:
I'm trying to replicate the positive results of the Client/Server
scripts from the thread "Bidirectional Networking", but this time
using a Process/SubProcess architecture.
The SubProcess, acting as a server, is working just fin
