Gopinath (9711107) wrote:
> > Define "a segment"? Do you mean an IP datagram or fragment? If so
> > then the answer is... Of course. That's not even necessarily under control
> > of the application.
>
> >
> > TCP/IP is basically a stream of data with a few "Out Of Band"
> > signalling conventions. Lots of the protocols such as smtp, ftp, http,
> > etc, etc, use a line oriented protocol. They send ascii commands which
> > are delimited by new lines, generally a CR/NL termination. A command
> > may be split across several IP datagrams at the discretion of the low
> > level protocol stacks (subject to the absence of the "do not fragment"
> > option). The server at the other end merely reads lines. It does not
> > know or care if that line came across on one, two, or more datagrams.
>
> ---------> I meant the segment to be the unit of data that TCP
> gives to the IP and asks it to send to some destination.
>
> Is it possible that TCP might give to the ip "PU" first,
> and T the next time?
It is possible, although unlikely.
In general, the client will read the response from one command before
sending the next command, so I would expect there to be a one-to-one
correspondence between commands and IP datagrams. However, this cannot
be guaranteed.
--
Glynn Clements <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
