Bjoern Schliessmann wrote:
Whoops, the TCP client does in fact quit if the server closes
connection :)
Great - so it wasn't a problem with the TCPClient after all :-)
For some reason, my Listener doesn't quit. I thought
it's sufficient to exit the main method in some way to quit a
Michael Sparks wrote:
It is sufficient, and running with Kamaelia from /trunk, your
listener does indeed shutdown correctly
Great, thanks for validating. :)
My suggestion for the moment would be to use the code on /trunk
since this is stable at present (development happens on branches
Michael Sparks wrote:
The behaviour you're seeing sounds odd (which is hopefully
encouraging :-), but it's not clear from the description whether
its a bug in your code or Kamaelia. One question I really have as
a result is what version are you using?
Oh sorry, it's the versions from MegaPack
Bjoern Schliessmann usenet-mail,,...m wrote:
I'm currently trying to implement a simulation program with Kamaelia
and need a reliable TCP connection to a data server.
From Twisted, I know that a method is called if the connection fails
by whatever reason. I tried to get the same results with
Hendrik van Rooyen wrote:
Not sure about Kamelia, but I have found that when a FIN comes
along, a socket.recv() gives back an empty string, just like EOF
on a file.
That Python socket interface can detect it I'm absolutely sure --
Twisted handles it.
I even pdb'ed Kamaelia and control flow
Bjoern Schliessmann wrote:
Hello,
I'm currently trying to implement a simulation program with Kamaelia
and need a reliable TCP connection to a data server.
The behaviour you're seeing sounds odd (which is hopefully encouraging :-),
but it's not clear from the description whether its a bug in
Hello,
I'm currently trying to implement a simulation program with Kamaelia
and need a reliable TCP connection to a data server.
From Twisted, I know that a method is called if the connection fails
by whatever reason. I tried to get the same results with Kamaelia's
TCPClient component. If I
