RE: Re[4]: [clisp-list] TCP-based Network Server in CLISP

[Dave R. <da...@sy...>]

> Do you want OOB data handling ? My familiarity with OOB was ended up with
> this (MSDN)

The TELNET protocol defines a sequence called "synch" which does use urgent
data.  My server is a TELNET server.  So, yes, I need OOB to handle "synch"
correctly (on input).  I never generate a "synch" back to the client.

> "To minimize interoperability problems, applications writers are
> advised not
> to use OOB data unless this is required to interoperate with an
> existing service."

It is.  However, I intend to use the (:so-oobinline t) socket option, so the
OOB data will be delivered "in-band".

> If you want to know if recv or send operation will succeed you can use
> select and filter some situations, but there can be no guarantee that
> such operation will succeed. I think only way is to use handler-case
> or something like it. Do you want to avoid handler-case ?

My hope was that I'd mark the socket non-blocking and do partial
reads/writes.  I have not started reading the I/O functions yet.  I think
Sam has successfully demonstrated that socket-status ought to meet my needs
for select().  Sadly, I have to do time-differencing, but it works in the
current server, so...  And besides, if that's the only down-side to porting
to CLISP, it's hardly worth mentioning.

	Thanks!

	Dave