Re: clisp-cvs Digest, Vol 59, Issue 7 - econnreset

[Sam S. <sd...@gn...>]

> * Don Cohen <qba...@vf...> [2011-04-11 13:08:45 -0700]:
>
> Sam Steingold writes:
>  > > * Don Cohen <qba...@vf...> [2011-04-11 10:31:12 -0700]:
>  > >
>  > > My first suggested patch would be to move this statement close to the
>  > > top of the doc.
>  > >   This is the interface to select (on some platforms, poll) ...
>  > 
>  > we specify the underlying posix call at the _end_ of the docs for
>  > each function.
>
> The meaning of :error is hard to describe without referring to select.
> Are forward references allowed?

yes, this is lisp, not ML.

>  > > What counts as a pending error?  RST?  EOF?
>  > RST is an error; EOF is not.
> In that case, rst should cause socket-status to return :error, right?

I agree.

>  > This is best discussed on comp.protocols.tcp-ip
>  > Please _do_ take this discussion there, and report back with your findings.
>
> I don't think this is a tcp question.  I think it's more like posix.
> Or perhaps even more specific, linux, windows, etc.

Whatever.  This is certainly not a clisp question.
I am sure comp.protocols.tcp-ip people will either answer the
question straight away, or tell you where to ask.

>  > again, comp.protocols.tcp-ip is your friend.
>  > the translation for them:
>  > - why does select() return -1 and set errno=ECONNRESET instead of
>  > returning the socket in the errorfds set?
> Again, this is not related to tcp (or ip), but to the OS interface.

make your choice.

> BTW, is windows supposed to be posix compliant?

yes, if you buy a posix compatibility layer :-)

> > RFC793 describes situations when the recipient of RST goes into LISTEN
> > and not ABORT states.
>
> Perhaps we should not use the term "socket" here but "connection".
> When you go into listen state you're looking for requests to start
> new connections.  Another request to start a connection on the same
> socket may succeed, even from the same port on the same peer ip
> address, but it will be a new connection.  You're supposed to send a
> reset for a connection when that connection, as far as you are
> concerned, is already dead, or never existed to begin with.

Ah, this is highly illuminating.  Thanks!

-- 
Sam Steingold (http://sds.podval.org/) on CentOS release 5.5 (Final) X
http://www.PetitionOnline.com/tap12009/ http://palestinefacts.org
http://memri.org http://jihadwatch.org http://mideasttruth.com
Live Lisp and prosper.