On Sun, 20 May 2007 18:28:22 +0200 Tilman Sauerbeck <tilman@...>
> Chris Stromblad [2007-05-20 14:58]:
> Hi Chris,
> > Yeah thanks, I did figure it out in the end. There are however something
> > that I would consider a bug. Obviously it's also likely it's simply me
> > who are not using it correctly.
> > Such as: If I connect to a web server and use HTTP/1.0. The server will
> > disconnect after sending the requested resource. However, if I use
> > ecore_con_server_connected_get, it will still report as being connected.
> > Trying to send something using the server handle will fail, yet the
> > 'connecting' (the one inside the server struct in ecore_con.c/h)
> > variable will not be updated. Or so it seems.
> Do you have an event handler for the SERVER_DEL event? It will be
> triggered if the remote end closes the connection, IIRC.
> That won't fix the behaviour of _server_connected_get(), but it might
> give you a neater way of figuring out whether your connection is in a
> nice state or not ;)
yup. use the server add and dell events. yo get the add (as a client) when you
connection has succeeded. you get the del when you have been disconnected.
ecore_con cunningly buffers any data u send before it has become connected and
will flush it for you on connect. once you have been disconnected the server
handle is in a strange state - its alive waiting deletion (you should call
server_del now). the is_connected call was meant primarily for before you get
the server_add event as it is expected you will delete the server on a
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing on usenet and in e-mail?
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler) raster@...
Tokyo, Japan (東京 日本)