directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alessandro Torrisi <>
Subject Re: [Mina] 'messageSent' semantic
Date Wed, 11 Jan 2006 18:23:24 GMT
Hi ! Hi there is something confused.

I think that the meaning of the posts was that it's not Java that has  
to take care of transport...
but it's care of the TCP-IP stack implemented in each operating system.

I've read the posts on the Java forum and it's really not clear.

In my poor opinion, I think that differences between TCP/IP and UDP  
protocol are here !
TCP has the SYN-ACK system which is at the base of the communication  
control among
hosts. If a message has not come, or if its sequence is not right,  
packet is retransmitted
to ensure packet delivery, I'm agree with J-F.

If not so, what's the sense of TCP/IP ??? Use UDP...

I hope I have not understood that post or I will be in doubt on  
myself and with all the documentation
I've read...

Best regards, Alex

On 11/gen/06, at 18:59, wrote:

> Quoting Niklas Therning <>:
>> wrote:
>>> ...
>>> Do you mean that when the call
>>> socket.getOutputStream().write(myBufferOf1000Bytes) returns, it  
>>> does not mean
>>> that all 1000 bytes has been transmitted via TCP/IP to receiver?
>>> What does it mean then? That the 1000 bytes are in TCP/IP stack's  
>>> buffer?
>> Yes, I think so.
>> Read this post:
>> /Niklas
> Thanks. The post is not so clear.
> I am surprised it is stated that TCP does not guarantee that  
> message is
> received. It does so. It guarantees packet delivery and packet order.
> I guess they meant that with sockets, reception at TCP/IP level  
> does not imply
> consumption of the buffer by the receiving program.
> J-F

View raw message