Rich Salz <[EMAIL PROTECTED]> writes:
> Data may be coalesced. It does not HAVE to happen but it MAY happen.
>
> Note that TCP does not preserve record boundaries: two writes may end up
> being read in three parts, e.g.
>
> What you're seeing is just a circumstance of your network setup. No
Data may be coalesced. It does not HAVE to happen but it MAY happen.
Note that TCP does not preserve record boundaries: two writes may end up
being read in three parts, e.g.
What you're seeing is just a circumstance of your network setup. No
guarantees.
/r$
_
"kaushik_vishwakarma" <[EMAIL PROTECTED]> writes:
> [1 ]
> hi,
>
>
> the specification of ssl says that in the record layer messages
> can get coalesced. But i did not see this happening in my test
> program. my test program had one server and one client. the server
> after accepting c
hi,
the specification of ssl says that in the record layer messages can get coalesced. But i did not see this happening in my test program. my test program had one server and one client. the server after accepting connection reads 16 kb of data at a time. The client sends two messages both more t
