Slashdot Mirror


Interoperable P2P: Jxta

Troy writes: "This article went up today (on developerWorks) about the Open Source project called Jxta, which is a community-run attempt to build a utility application substrate for peer-to-peer applications. Anything with an electronic heartbeat can become a Jxta peer." A nice high-level overview of how Jxta is supposed to work.

2 of 75 comments (clear)

  1. Java, JINI, JXTA... by MosesJones · · Score: 5, Interesting


    Sun are a strange bunch, a company where the vi v emacs wars can really kick off as two of the developers are there (Gosling for emacs, Joy for vi). JXTA is another of Bill Joy's babies, its meant to be a language/protocol independent offering for peer to peer solutions, which was originially what http://www.jini.org said they would do (Jim Waldo).

    JXTA is a nice idea, and there are some good papers from JavaOne on the subject. But given that Sun's marketing might is behind J2EE will JXTA really be given a chance ?

    IMO the answer is probably yes, JXTA and Java are part of a two pronged attack at next generation devices, this isn't really PC to PC type applications but device to device, most of the next generation mobiles will be running Java, some will not and most service provider cells will not, JXTA enables the bridge between the Java world of the device and the big bad world of networking to interact.

    Strange how the best ideas come without marketing strategies. Java was an inhouse project which aimed for 10,000 downloads. Will the same explosion happen with JXTA in a wireless world ?

    PCs suck, time to distribute.

    --
    An Eye for an Eye will make the whole world blind - Gandhi
  2. Jxta is not all that by hardburn · · Score: 5, Insightful

    Jxta was created by Sun to be a "framework" for P2P networks. What exactly that means is rather vague. It appears to make basic development decisions that are better left up to indiviual projects (such as broadcast seaches). TCP/IP is really the only thing most P2P networks have in common, and even that could often be easily replaced with a diffrent underlieing protocol if it was necessary.

    There are several other assumptions that Jxta makes that it shouldn't. See this article for more information.

    --
    Not a typewriter