P
Patrick Useldinger
Has anybody got such an example? My server works fine, but my client
does not :-(
does not :-(
Erik said:I tried to run your sample but you didn't include enough material for me
to run it as a standalone application. When I tried to stub out the
additional material you didn't include, I got connection refused errors,
presumably because the server wasn't running at the point your clients
tried to connect.
Patrick said:This is exactly what seems to happen with the async_chat class, as in
dispatcher.create_socket the same setblocking(0) is done.
If you just could shed some light on what this error means, I haven't
found any explanation up to now.
Heiko said:Remember: connecting is also a non-blocking operation, if the socket is
set to non-blocking mode.
I dunno why async_chat doesn't work with this on Windows (on *nix, this
is exactly what it does), but I guess it has something to do with
decoding the error codes, as a *nix-socket would return EWOULDBLOCK in
this case, for which it checks, I am certain of that.
Erik said:The bigger question is why you're asking the socket to not block when it
appears that you really want it to (since your logic isn't handling the
case when it doesn't).
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.