Re: [Pharo-project] Networking problems on Pharo 1.2.1

2011-04-21 Thread Göran Krampe
On 04/21/2011 07:17 AM, Oscar E A Callau wrote: Hi again, I found a solution (but not what was the problem); change the server code to the following: Just a tip: Please use SocketStream, it will help you when doing the actual sending/receiving. In almost every situation SocketStream is your

Re: [Pharo-project] Networking problems on Pharo 1.2.1

2011-04-21 Thread Luc Fabresse
Hi, Yes SocketStream is useful but still, the socket base layer should be usable without problems ... I do not know why #waitForAcceptFor: do not make it. #Luc 2011/4/21 Göran Krampe go...@krampe.se On 04/21/2011 07:17 AM, Oscar E A Callau wrote: Hi again, I found a solution (but not

Re: [Pharo-project] Networking problems on Pharo 1.2.1

2011-04-21 Thread Stéphane Ducasse
+1 I would love to know the answer. On Apr 21, 2011, at 9:26 AM, Luc Fabresse wrote: Hi, Yes SocketStream is useful but still, the socket base layer should be usable without problems ... I do not know why #waitForAcceptFor: do not make it. #Luc 2011/4/21 Göran Krampe

Re: [Pharo-project] Networking problems on Pharo 1.2.1

2011-04-21 Thread Sven Van Caekenberghe
On 21 Apr 2011, at 09:26, Luc Fabresse wrote: Yes SocketStream is useful but still, the socket base layer should be usable without problems ... +1 Both should work, both should be understandable by mere mortals like us.

Re: [Pharo-project] Networking problems on Pharo 1.2.1

2011-04-21 Thread Stephan Eggermont
That is no networking problem. That is just how a tcp server connections work. When you connect from a client to the server, the server has to initialize a new socket to communicate on. Just take a look at what waitForConnectionFor does. Stephan

Re: [Pharo-project] Networking problems on Pharo 1.2.1

2011-04-21 Thread Sven Van Caekenberghe
On 21 Apr 2011, at 12:42, Stephan Eggermont wrote: That is no networking problem. That is just how a tcp server connections work. When you connect from a client to the server, the server has to initialize a new socket to communicate on. Just take a look at what waitForConnectionFor does.

Re: [Pharo-project] Networking problems on Pharo 1.2.1

2011-04-21 Thread Oscar E A Callau
Thanks all for your comments. On Apr 21, 2011, at 07:13 , Sven Van Caekenberghe wrote: I think the problem might be the #listenOn: I use #listenOn:backlogSize: These are using different primitives. I tested with #listenOn:backlogSize: too, with the same result, error on

Re: [Pharo-project] Networking problems on Pharo 1.2.1

2011-04-21 Thread Oscar E A Callau
Thank you very much Sven, I think this must be include in the pharo book, because it was hard to find good examples. Cheers. On Apr 21, 2011, at 08:22 , Sven Van Caekenberghe wrote: Oscar, This is how I would write it, using first SocketStreams (which is better for most users) and then

Re: [Pharo-project] Networking problems on Pharo 1.2.1

2011-04-21 Thread Stéphane Ducasse
Yes I forwarded that mail to the network chapter authors. and we will really ask for feedback Stef On Apr 21, 2011, at 4:06 PM, Oscar E A Callau wrote: Thank you very much Sven, I think this must be include in the pharo book, because it was hard to find good examples. Cheers. On

Re: [Pharo-project] Networking problems on Pharo 1.2.1

2011-04-20 Thread Oscar E A Callau
Hi again, I found a solution (but not what was the problem); change the server code to the following: |port msg| port:= 9191. Transcript open; show: 'testing --- ' ; cr. listening := true. [self isListening] whileTrue: [