For the last two years, we have been working on something extremely similar: Jtrix
Technically, Jtrix has micro-kernel-like agents (nodes) running on host machines. Applications consist of code fragments that can be executed on the nodes. There is a mechanism for binding to a remote service, and that's pretty much all you need as a basic platform. Of course, it's convenient to have some support services (eg. file storage), but that's already in userland (as it should be).
A lot of this is implemented and working. We have got one problem though: we need a killer app to get people running thoses nodes...
GPS has a number of limitations which would
curtail the usefulness of such a phone:
the GPS signal does not penetrate solid objects (walls, windows, car ceilings)
you need to have a clear line-of-sight to at least 3 satellites (which is difficult on a downtown street)
it takes considerable time to get a location fix from a "cold" receiver (eg. after taking your phone out of the pocket).
GPS receivers seem to be quite power-hungry
I guess this makes it useful if you have the phone in the car, hooked up to the car's power supply and antenna. Not very good though for city animals like myself!
Personally, I'd like to see base-state triangulation done by the phone combined with GPS. That would be cool.
I couldn't agree more. Even P2P needs some
hierarchical structures.
The interesting question is whether you want
the hierarchy internally, or whether you want
to factor it out. I'd go for the latter -
ultimately arriving at some sort of framework where your P2P application is actually composed of many other services (which might even be provided by other P2P communities). Call it Internet II !
Having said that, JXTA is really not meant to
address this. But someone will.
Slashdot Mirror
For the last two years, we have been working
...
on something extremely similar:
Jtrix
Technically, Jtrix has micro-kernel-like agents (nodes)
running on host machines. Applications consist of
code fragments that can be executed on the nodes.
There is a mechanism for binding to a remote service,
and that's pretty much all you need as a basic
platform. Of course, it's convenient to have some
support services (eg. file storage), but that's
already in userland (as it should be).
A lot of this is implemented and working.
We have got one problem though: we need a killer
app to get people running thoses nodes
curtail the usefulness of such a phone:
I guess this makes it useful if you have the phone in the car, hooked up to the car's power supply and antenna. Not very good though for city animals like myself!
Personally, I'd like to see base-state triangulation done by the phone combined with GPS. That would be cool.
I couldn't agree more. Even P2P needs some hierarchical structures. The interesting question is whether you want the hierarchy internally, or whether you want to factor it out. I'd go for the latter - ultimately arriving at some sort of framework where your P2P application is actually composed of many other services (which might even be provided by other P2P communities). Call it Internet II ! Having said that, JXTA is really not meant to address this. But someone will.