For a future release of P2P Sockets, I've thought about giving every "site" a "search" interface, which would really be a way to access the rendezvous peers for that peer group. Programmers would then simply feel like they are calling the search CGI-BIN for a site when in fact they are calling the rendezvous peers. This search interface could either be exposed as a standard part of the URL, such as "www.nike.laborpolicy/search?type=PeerAdvertisement&name=BradNeuberg"
or it could be exposed as a standard port number that you post the information to. What could be returned would simply be a multi-part document of Jxta advertisements, which is simple, but it does expose some Jxta stuff. That's not necessarily bad if it solves the problem.
One thing I'm concerned about, however, is that I want to have some concrete "problems" that are trying to be solved before I start creating ungrounded mechanisms.
or it could be exposed as a standard port number that you post the information to. What could be returned would simply be a multi-part document of Jxta advertisements, which is simple, but it does expose some Jxta stuff. That's not necessarily bad if it solves the problem.
One thing I'm concerned about, however, is that I want to have some concrete "problems" that are trying to be solved before I start creating ungrounded mechanisms.
Comments