A search in google images for sockets state diagram comes up with some relatively good ones http://images.google.com/images?hl=en&um=1&sa=3&q=sockets+state+diagram&btnG=Search+images Most of them are just the TCP connection state logic, but I'm sure I'd find others there if I looked closer.
- Job On Wed, Jun 24, 2009 at 3:11 PM, Johan Tibell <johan.tib...@gmail.com>wrote: > On Wed, Jun 24, 2009 at 8:16 PM, Brandon S. Allbery KF8NH < > allb...@ece.cmu.edu> wrote: > >> The BSD socket protocol is explicitly driven by a state machine, btw, but >> it's a fairly complex one. Also, it's generally described in terms of the >> kernel's view, which includes states you normally can't distinguish in a >> user program (for example, a socket in TIME_WAIT keeps its port unavailable >> unless you use SO_REUSEADDR, but is otherwise indistinguishable from a >> socket which has been close()d and reaped). >> > > I've been looking for a state diagram for this state machine for e.g. Linux > but my google-fu has failed me so far. Do you have a reference? > > -- Johan > > > > _______________________________________________ > Haskell-Cafe mailing list > Haskell-Cafe@haskell.org > http://www.haskell.org/mailman/listinfo/haskell-cafe > >
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
