Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.misc > #8180 > unrolled thread

What stacks are there in TCP

Back to article view | Back to comp.os.linux.misc

Contents

  What stacks are there in TCP fl <rxjwg98@gmail.com> - 2013-05-18 14:47 -0700
    Re: What stacks are there in TCP David Hough <noone$$@llondel.org> - 2013-05-22 07:35 +0100

#8180 — What stacks are there in TCP

Hi,

Excuse me, I post this question because I do not know other group can be fit for it. Please tell me if you know a more relevant group. I read an article on raw API, see below please. I do not know what it means for "other TCP stacks". Could you explain it to me?


Thanks





..................
The raw API is customized for high performance and lower memory overhead. The
limitation of raw API is that it is callback-based, and consequently does not provide portability to other TCP stacks.

[toc] | [next] | [standalone]

#8185

fl wrote:

> Hi,
> 
> Excuse me, I post this question because I do not know other group can be
> fit for it. Please tell me if you know a more relevant group. I read an
> article on raw API, see below please. I do not know what it means for
> "other TCP stacks". Could you explain it to me?
> 
TCP stack is the name given to an implementation of TCP. "Other TCP stacks" 
is a reference to other implementations. While a fair few modern stacks are 
based on a common source and have a reasonably common API, there are others 
which were written independently and so may not have the same API. Think of 
a stack as a black box which talks TCP at one end and has a set of hooks at 
the other end to which you can attach your application. Different stacks 
might not have the hooks in the same place.

All it's saying is that if you write code to use a particular stack via its 
API, you might not be able to easily port it to another stack.  

Dave

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.misc

csiph-web