dev@glassfish.java.net

Re: About NonBlockingWireOutputPipe's TTL Setting

From: <justin_at_lifeasageek.com>
Date: Tue, 11 May 2010 06:16:55 +0000

Is this not because peer discovery needs to take place and if the message expires too quickly this peer discovery may not take place?
------Original Message------
From: Wu Jie
To: dev_at_jxta.dev.java.net
To: dev_at_glassfish.dev.java.net
Cc: adamman71_at_dev.java.net
Cc: shreedhar_ganapathy_at_dev.java.net
ReplyTo: dev_at_glassfish.dev.java.net
Subject: About NonBlockingWireOutputPipe's TTL Setting
Sent: May 11, 2010 07:31

Hello JXTA Dev Team
Hello GF Shoal Dev Team

Sorry for interrupting you.

I come from Fujitsu China and have sth doubt about TTL(time to live) setting
in JXTA's implementation(JXSE).

[Problem]
jxse-src-2.5\impl\src\net\jxta\impl\pipe\NonBlockingWireOutputPipe.java
------------------------------------------------------------
public boolean send(Message message) throws IOException {
       ... ...
       WireHeader header = new WireHeader();
       header.setPipeID(getPipeID());

       header.setTTL(destPeers.isEmpty() ? 200 : 1); //★My Problem
       ... ...
}
------------------------------------------------------------
★My Problem:
Is there any special purpose to set TTL to 200 when destPeers is empty?
#why not be set to any other number?

[Background of Problem]
If TTL is set to a big number, I think it may lead bad influence to the overhead
of network. To put down the overhead of network, may I set a number less than 200
for TTL when destPeers is empty?

Could you please give me any comment or suggestion? Any help will be appreciated.

Best Regard
Wu Jie



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: dev-help_at_glassfish.dev.java.net



Sent from my BlackBerry® wireless device