On Jan 14, 2011, at 10:56 AM, Kai Renz wrote:
Hi there,
i'm currently working on a socket project. It consists of two scripts.
The first script (socket1.php) creates a socket on a specified port
and waits for a client to connect. If a client connects, they exchange
some informations,
On Fri, Jan 14, 2011 at 11:56, Kai Renz writeme...@googlemail.com wrote:
Now here is the problem:
it all works fine, but the client can't send a quit message to socket1
because socket1.php waits until socket2.php is finished. socket2.php
is working properly, and if i connect to the new socket
On Fri, Jan 14, 2011 at 13:28, Kai Renz writeme...@googlemail.com wrote:
(Putting this back on the list. Please use Reply-All.)
@Daniel:
Yeh i tried sending it to the background, this works but still it does
wait for the other script to finish.
It shouldn't. In fact, just to see if
Hi guys and thanks for your answers...
@Nicholas:
Yes, you are right. The first socket is only used if a new clients
connects, thats why the script generates a new port so the client can
connect to the new socket. After that socket1 should continue its work
and wait for new clients.
@Daniel:
Yeh
On Jan 14, 2011, at 12:41 PM, Kai Renz wrote:
Hi guys and thanks for your answers...
@Nicholas:
Yes, you are right. The first socket is only used if a new clients
connects, thats why the script generates a new port so the client can
connect to the new socket. After that socket1 should
On 14 January 2011 18:48, Nicholas Kell n...@monkeyknight.com wrote:
On Jan 14, 2011, at 12:41 PM, Kai Renz wrote:
Hi guys and thanks for your answers...
@Nicholas:
Yes, you are right. The first socket is only used if a new clients
connects, thats why the script generates a new port so the
6 matches
Mail list logo
