Re: [clisp-list] errors from socket-status

[<don...@is...>]

I just notice that socket-status returns two values, while the doc
only mentions one.
This confused me when I saw the output of
  (multiple-value-bind 
    (val err) 
    (ignore-errors (ext:socket-status *socket-status-arg* time)) 
    (when err 
      (http::logform (list :http :socket-status-err 
                           (http::print-current-time nil) 
                           err))            ))
Sam Steingold writes:
 > Don Cohen wrote:
 > >  > if you have a reproducible case, I am interested.
 > > It happens regularly, so I can reproduce it in that sense.
 > > If I record the relevant packets then I suppose it should
 > > be possible to reproduce it on demand by some approximation
 > > of replay.  Or perhaps it would suffice for a start to simply
 > > describe the packet(s) that cause the error.  Shall we start
 > > with that?
 > 
 > I would prefer something like "start clisp, open socket server, connect to it 
 > from another shell using telnet, type '...' to telnet, kill telnet, type '...' 
 > to clisp, observe the error".