RE: Peers do not find each other

You are very much right with your view of connecting to the rdv peer
before going any further.

The solution that I have given is very much specific to the original
problem of Matthias Horst.

In his eamil he has given the following background:
...................I do *not* configure any rendezvous peers, because
for my projekt a want to give away just a CD with the Peer-2-Peer
Software and everybody in the same network, who uses the CD, should find
all the other users automatically, without asking a administrator for
settings. (At least that's the idea).

We all agry that we need no rdv peer when the peers are in same network
and therefore I have given such a solution. When one do not have a rdv
peer than why to write a code for connecting to the rdv? why to give a
false rdv address (as stated in the original problem description)?

I think I have cleared the doubt raised about this solution.

______________________________________________________
Rahul A. Dolas
SETLABS
Infosys Technology Ltd.
Plot No. 1, Pune Infotech Park,
Pune 411027 India
Ph: +919890285220
[email protected]
[email protected]
_____________________________________________

-----Original Message-----
From: Sayed Hashimi [mailto:[email protected]]
Sent: Wednesday, August 10, 2005 10:59 AM
To: [email protected]
Subject: Re: [JXTA user] Peers do not find each other

I don't agree with this. In all the applications that I've developed if
we were not connected to a RDV before starting communication problems
would arise. If you are running private peer groups or your own
NetPeerGroup then you should definetly wait to be connected to the RDV
before you start anything up. From my experience it is generally better
to wait for a RDV connection. In our situation we have a custom RDV so
we don't exaclty have the option to allow just any peer to be come a
RDV.

Sayed Ibrahim Hashimi

On 8/10/05, Rahul Dolas <[email protected]> wrote:
>
> Why are u writing a code in the program for connecting to a rendezvous
> peer?
> Don't write any such code which stops ur program going further when it
> is not connected to the rendezvous peer. The connection to the
> Rendezvous peer is not necessary for any peer, and peer do not try to
> connect the Rendezvous peer on it's own. We through our program ask a
> peer to connect to the Rendezvous.
>
> Refer the examples in the Developers guide and I think it will clear
> my point to you in a better way.
>
>
>
> ______________________________________________________
> Rahul A. Dolas
> SETLABS
> Infosys Technology Ltd.
> Plot No. 1, Pune Infotech Park,
> Pune 411027 India
> Ph: +919890285220
> [email protected]
> [email protected]
> _____________________________________________
>
> -----Original Message-----
> From: Bernard Traversat [mailto:[email protected]]
> Sent: Wednesday, August 10, 2005 6:38 AM
> To: [email protected]
> Subject: Re: [JXTA user] Peers do not find each other
>
> Matthias Horst wrote:
> >
> > Then I stop peer A (the rendezvous) and restart it.
> >
> > Again they don't find each other.
> >
> > Question:
> > ------------
> > Is anybody out there who can explain this behaviour?
> Likely your Peer A RDV configuration is incorrect or Peer B seeding to
> RDV A is incorrect.
>
> > I thought that at
> > least in the same subnet all peers find each other automatically as
> > long as multicast is enabled even without an explicit rdv peer.
> You are correct. If multicast is enabled you don't need any RDVs.
>
> I suggest you start with the Shell (shell.jxta.org). Are you using
> ext:config to configure your peers
>
> Hth,
>
> B.
>   Obviously as
> > soon as peer A is offline for some seconds every communication
> > between
> A
> > and B seems to be impossible. I don't think that you guys out there
> are
> > using a p2p network where everybody must reboot his application
> because
> > somebody else shutdown his peer ;) So what's the trick?
> >
> >
> >
> > greetings
> >
> >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: [email protected] For additional
> > commands, e-mail: [email protected]
> >
>
>
> --
> --http://weblogs.java.net/blog/tra
> "As Java implies platform independence, and XML implies language
> independence, JXTA implies network independence."
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected] For additional
> commands, e-mail: [email protected]
>
>
> **************** CAUTION - Disclaimer ***************** This e-mail
> contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for
the use of the addressee(s). If you are not the intended recipient,
please notify the sender by e-mail and delete the original message.
Further, you are not to copy, disclose, or distribute this e-mail or its
contents to any other person and any such actions are unlawful. This
e-mail may contain viruses. Infosys has taken every reasonable
precaution to minimize this risk, but is not liable for any damage you
may sustain as a result of any virus in this e-mail. You should carry
out your own virus checks before opening the e-mail or attachment.
Infosys reserves the right to monitor and review the content of all
messages sent to or from this e-mail address. Messages sent to or from
this e-mail address may be stored on the Infosys e-mail system.
> ***INFOSYS******** End of Disclaimer ********INFOSYS***
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected] For additional
> commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional
commands, e-mail: [email protected]