A socket should be closed when you receive a "\n", followed by a ".", followed by a "\n". These will not necessarily all be returned by one recv() call, so you will have to find some way to keep track of, at the minimum, the last 2 characters that were received on a given socket in addition to the character(s) returned by another recv() call.<br>
<br>--Joe<br><br><div class="gmail_quote">On Fri, Sep 25, 2009 at 6:20 PM, Tim Miller <span dir="ltr"><<a href="mailto:mille449@msu.edu" target="_blank">mille449@msu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
For the non-blocking server, how do I tell when a socket should be closed?<br>
<br>
<br>
<br>
--Tim<br>
<br>
On Fri, Sep 25, 2009 at 6:19 PM, Tim Miller <<a href="mailto:mille449@msu.edu" target="_blank">mille449@msu.edu</a>> wrote:<br>
> working now.<br>
><br>
> On Fri, Sep 25, 2009 at 5:37 PM, C. Titus Brown <<a href="mailto:ctb@msu.edu" target="_blank">ctb@msu.edu</a>> wrote:<br>
>> Fudge. Out of town. I will diagnose and fix...<br>
>><br>
>> ---<br>
>> C. Titus Brown, <a href="mailto:ctb@msu.edu" target="_blank">ctb@msu.edu</a><br>
>><br>
>> On Sep 25, 2009, at 4:31 PM, Tim Miller <<a href="mailto:mille449@msu.edu" target="_blank">mille449@msu.edu</a>> wrote:<br>
>><br>
>>> I can't reach the svn server. It was working ~15 min ago but it is<br>
>>> not now. There any problems with it?<br>
>>><br>
>>> Had two questions originally, but figured out the other one while<br>
>>> typing it up. silly how that works ;)<br>
>>><br>
>>> Thanks<br>
>>><br>
>>> Tim Miller<br>
>><br>
><br>
<br>
_______________________________________________<br>
cse491-fall-2009 mailing list<br>
<a href="mailto:cse491-fall-2009@lists.idyll.org" target="_blank">cse491-fall-2009@lists.idyll.org</a><br>
<a href="http://lists.idyll.org/listinfo/cse491-fall-2009" target="_blank">http://lists.idyll.org/listinfo/cse491-fall-2009</a><br>
</blockquote></div><br>