|
Re: Testing socket for disconnect: msg#00033lib.boost.asio.user
To answer you first question - as I understand it, there's no way to tell if the socket is still connected without select()-ing* on it. So you will need some sort of session-layer protocol no-op command that can be sent at intervals to poll for (detect) disconnections. I may be wrong! Richard * or kqueue(), poll(), epoll() etc, performed by boost::asio On 11/29/06, Stas Khirman <staskh-Wuw85uim5zDR7s880joybQ@xxxxxxxxxxxxxxxx> wrote: > Hi, > > What is 'ASIO-approved' way to check if TCP socket had been disconnected by > remote peer while no outstanding read/write operation. > > Related question - Did I understand correctly that if I have an outstanding > read/write it will be completed with asio::error:: connection_aborted error > on remote peer disconnect ? . > > Stas > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > asio-users mailing list > asio-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx > https://lists.sourceforge.net/lists/listinfo/asio-users > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Testing socket for disconnect: 00033, Stas Khirman |
|---|---|
| Next by Date: | Re: Testing socket for disconnect: 00033, Richard Dingwall |
| Previous by Thread: | Testing socket for disconnecti: 00033, Stas Khirman |
| Next by Thread: | Re: Testing socket for disconnect: 00033, Richard Dingwall |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |