Re: trouble finding peers

Hybrid solutions can/should be explored as well. There may be services 
available based on
your deployment domain that can be leveraged. As an example, MyJXTA does 
have support
for LDAP authentication (/net/jxta/myjxta/util/LDAPAuthenticator) that I 
have used when
deploying MyJXTA for classic intranet deployments ... where the 
peer|user domain is
bounded, in my case each designated with unique employee ids. In this 
case, I was able
to generated pipe id's seeded with the employee id. in this scenario, it 
wasn't necessary
to discover "peers" but I could instead try to connect to "well known" 
instances (eg buddies)
directly to test for connectivity, etc.

In short, keep thinking, keep trying, keep exploring, keep sharing and 
lastly ... keep doing :)

hth,

- james

--

James Todd :: blogs.sun.com/gonzo | weblogs.java.net/blog/gonzo

MyJXTA :: use it - learn it - do it

Java == platform independence
XML  == application independence
JXTA == network independence

Secure End-to-End Computing 



Steven Myers wrote:

>Hi James, I was afraid using pipe advertisements might be hack but since
>you're doing it that way in myJXTA that's good enough for me.  I'll just
>based my presence functionality on pipes too and move on to the fun
>stuff (I'm working on a little p2p game using jxta+java3d).  Thanks for
>your help! 
>
>-- Steve  
>
>  
>