ONJava.com -- The Independent Source for Enterprise Java
oreilly.comSafari Books Online.Conferences.

advertisement

AddThis Social Bookmark Button
Article:
  The Trouble with JXTA
Subject:   alternates to heavy XML-based protocol approaches / sun's jxta fantasies
Date:   2001-05-08 18:12:23
From:   ceterusparibus
"XML can be many standards in a way, No?


If there are going to be all these devices then I perceive XML as the only way to go because you can have diversity within the standard of XML. A very Rich protocol indeed! So by the time p2p goes mainstream within gadgets and processing is up to par, jXTA should be there to take control. ;-)"


with all due respect, xml being many standards has nothing to do with anything. xml is like agreeing on an alphabet. you can form diverse (or even nonsense) words from the same alphabet, but that does not guarantee that those who agreed to the alphabet will understand the meanings of the words. understanding the meaning of these words is analagous to, as i said earlier, making protocols actionable.


again, xml is not a standard, nor a protocol. it is merely a standard way of specifying standards. since apps built on top of jxta will not have to deal with xml directly and will be leveraging the jxta api, the choice of xml is merely convenience for the jxta development team allowing them to take an off the shelf parser and use that to process messages.


sun is wrong. you don't make a protocol succesful by pushing it forward as a protocol. who cares about a protocol? not even the academics, beyond a certain point. what people care about is an application of the protocol (or any core technology for that matter) that can ONLY be accomplished reasonably well with this new protocol. i.e. a killer application. there is no killer app for jxta such that one couldn't do the exact same thing with a home-brew p2p protocol.


let's not fool ourselves. this is no great technological revolution, and it is not even a very interesting evolution. i am not microsoft lover, but the way they are approaching their messaging platform is much more mature. they want it to be adopted first, through massive dissemination of msn messenger and then hailstorm, finally tying all these "killer" apps which are widely adopted with a unified, underlying messaging platform. first come out with a cool application, then talk about the platform. this is not networks 301. this is th real world.