[cxml-devel] CXML vs usocket

David Lichteblau david at lichteblau.com
Wed Aug 29 12:15:57 UTC 2007


Quoting Magnus Henoch (mange at freemail.hu):
> With buffering enabled, this basically works.  However, I need to
> process "stanzas" (Jabber term for complete elements that are children
> of the root element) as soon as they come in, not when the buffer is
> full or when the stream or the root element is closed.  But when I
> disable buffering, I get (using CLISP from recent CVS):

Thanks for the report.  I have committed a bugfix to CVS.  Please test.

> It would be nice if this worked, and if additionally KLACKS:PEEK would
> do a non-blocking read.

I will have think about that one.  Would a function similar to LISTEN
also be okay, which would return T if data is available and NIL
otherwise?

(Note that it would not guarantee a non-blocking read if the server has
already sent some characters but not an entire event, and implementing
that cleanly would be a lot more difficult to do.)


d.



More information about the cxml-devel mailing list