<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/netclass/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/netclass/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Mon, 03 Sep 2001 07:46:36 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/netclass/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>trigger event on client termination</title><link>https://sourceforge.net/p/netclass/feature-requests/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;If the socket is closed by the client, we want to know about it!&lt;br /&gt;
Subsequent writing to the socket has undefined behaviour.&lt;/p&gt;
&lt;p&gt;Preferrably, a callback function can be registered to capture this event.&lt;br /&gt;
The callback should be passed an token that it defined for that socket.&lt;br /&gt;
And example might be:&lt;/p&gt;
&lt;p&gt;void OnClientDisconnect(int token) {&lt;br /&gt;
// do stuff&lt;br /&gt;
}&lt;/p&gt;
&lt;p&gt;....&lt;br /&gt;
socket-&amp;amp;gt;onClientDisconnect(OnClientDisconnect,1); // where 1 is the &lt;br /&gt;
token&lt;br /&gt;
.....&lt;/p&gt;&lt;/div&gt;</description><pubDate>Mon, 03 Sep 2001 07:46:36 -0000</pubDate><guid>https://sourceforge.net6c3bc24d28c7f81a3d170a1882f0c0f425f0f470</guid></item></channel></rss>