Hi Koen,
On 5 April 2011 17:32, Koen Deforche <[email protected]> wrote:
> Hey Bjorn,
[snip]
> Thanks for trying to find the culprit here. That seems indeed like the
> path to failure. The socket itself is created in:
>
> Server::startAccept() and Server::handleTcpAccept()
>
> There, one would expect that if the server indicates that a new
> connection was accepted without error (which is checked), the socket
> should be valid. Perhaps you can break there to look at the socket. It
> would be interesting to see why this is not the case and how the
> server example does this differently, assuming it also using
> async_accept ? (this is actually code that is inherited from the
> original http server example in boost::asio).
Yup, the boost server example is also using async_accept:
acceptor_.async_accept(new_session->socket(),
boost::bind(&server::handle_accept, this, new_session,
boost::asio::placeholders::error));
Thanks for the pointers. I'll take a look at it later. Don't hold your
breath though, this will be done in my spare time :-)
BTW, you wouldn't happen to know about what uClibc version and config
Wt has been tested with before?
Best regards,
Bjørn Forsman
------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest
