From: Iain Hanson (Iain.Hanson_at_[hidden])
Date: 2005-04-25 10:39:02
On Sun, 2005-04-24 at 17:45 -0700, Don G wrote:
> Hi Mats,
> It's good to have someone with experience in non-TCP environments!
> Glad you're here.
> > The X.25 API doesn't provide the equivalent to the tcp
> > listen(2) backlog parameter. To drive an X.25 acceptor
> > to be capable of accepting incoming calls at a high
> > rate, one has to implement the backlog oneself.
This is because you are doing this in the wrong place IMHO.
( see below ).
> Perhaps this is something that should be part of the impl of the
> acceptor for X.25. That would make X.25 and TCP the same in this
> sense (there are no doubt other differences of which this is just
No. You are comparing apples and oranges. TCP is a transport layer
protocol and X.25 is predominantly a Network layer protocol. A
connection Oriented equivalent to IP. The correct place to do this is
with a device driver 99.9% of the time.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk