Slashdot Mirror
Industrial-Strength P2P
hhutkin writes "Business 2.0 has an article in their latest issue on Bill Joy and Sun's peer-to-peer play, Jxta." A bit light on details but still good to know progress is being made in the field of peer to peer apps. But don't expect anything useful any time soon.
Sun has definately is omnious in its presence on unix market, but their contributions to unix communities, while cool for programmers - were not for sysadmin. RPC, NFS and NIS(+) were some the most exploted system blocks, running right behind bind and sendmail. Going to next point, does industrial strength means free gateways for hackers scanning cable and xDSL address ranges?
2c
Nobody's replying to this because all this article is doing is talking about some guy developing a P2P protocol.
... with this new protocol... a computer chip in my shoe can function as a "peer", but what the heck does that prove how robust this new protocol is going to be?
Gee whiz.... big news...
It's no different than making any other new protocol... the hard part is getting everyone to use it. And even though this article is titled "industrial strength", it doesn't elaborate on what makes this new protocol so "industrially strong". Does it use encryption? Respect copyrighted material? In bed with the RIAA? Who knows.... because this author certainly doesn't.
Yeah... sure
I am glad to hear some thing new out of the P2P industry even if it is so light on details.
THere are so many things that P2P seems like it would work great for so many things other then file exchange.
what uses does any one see for future use of P2P.
One use that I though of that could be cool it paying people to be part of a large scale cache of the net.. Well used web sites could make dynamicly mirror them selves very similar to the way Kazza and MORPHEUS Network share files.
What other uses do people see for P2P in the future?
Lets have fun!!
1. JXTA was written by a bunch of inexperienced Java developers. They broke all the rules of Java programming and wrote spagetti code. I think they discovered Design Patterns in the middle of their project and overused and abused them, yielding worse code.
2. They wrote demonstrations that used the pipe and filter architecture pattern to construct a unix shell essentially. One could list the peers on the network, pipe it through more, and wow your boss. But wait, it doesn't stop there - they created a chat program -- oooh.. IRC, IM anyone? When the time came to implement a real application, it was near impossible
3. The firewall/double firewall tunneling didn't work, so LAN deployment only folks!
4. The RVs, where peers gather and discover one another, were designed to only handle 10 socket connections, 4 of which were persistent. Nice and scalable! No failover support for the 1st release, BTW :)
5. There were a lot of holes in the specification and thus ports to other languages will yield them potentially incompatible above the basic network protocol(which is XML, BTW, and thus slow as binary exchange of files need to be BASE64 encoded)
6. The entire JXTA project is tagged as a research and development project only. This means that unlike Jini, which obtained a large marketing and development budget, Sun is throwing a lot of cheap developers and little marketing to this project.
In the end, it didn't deliver what it promised, it wasn't built for production use (Jini at least was, to some degree thank you Mr. Joy), and missed a lot of concepts necessary for effective peer networking.
Where are they now? Not sure.. We quit looking at their code around July and concentrated on other network alternatives - settling on Jabber.
What a disappointment!
Ever heard of samba? Windows file/print sharing?
Yep it's P2P
Yep it's useful
Thank you, and good night.
Apathy -- The state of numbness of the mind. When you are apathic, you can think.