Samuel,
Let me create a simple test case from the current code and I'll post it here.
El miércoles, 13 de marzo de 2013, Samuel Edwin Ward escribió:
Hi Roger/all,
I wasn't able to reproduce this with my setup; I seem to get the end of file condition either way.
I'm using usocket 0.6.0.1 on sbcl 1.0.54.0-185b926 on Mac OS 10.7.5.
Can you provide your versions and/or a runnable test case?
On Mar 13, 2013, at 12:24, Roger Sen Montero <roger.sen@gmail.com<javascript:_e({}, 'cvml', 'roger.sen@gmail.com');>> wrote:
Hi all!!
The FAQ states:
Reading from a stream which has been closed at the remote end signals an END-OF-FILE condition, meaning that reading from the stream and detecting that condition is the way to do it.
But when a create a server with:
:element-type 'character
I'm able to get an "Unexpected end of file" condition on the server side when the client disconnect.
Unfortunately, when I create the server with:
:element-type 'unsigned-byte
I do not get the condition, so I'm unable to detect when a client has disconnected.
Also, is there any plan to support utf8 streams directly without creating unsigned-byte sockets and converting from/to string to string-utf-8-bytes?
thanks!
Roger Sen Montero roger.sen@gmail.com <javascript:_e({}, 'cvml', 'roger.sen@gmail.com');>
usocket-devel mailing list usocket-devel@common-lisp.net <javascript:_e({}, 'cvml', 'usocket-devel@common-lisp.net');> http://lists.common-lisp.net/cgi-bin/mailman/listinfo/usocket-devel