doesn't tapestry sound like it should be written in erlang?
Martin J. Logan
Tue Nov 11 16:22:28 CET 2003
You have got to love reading "new" research along the lines of, each
overlay can be called a "node" and nodes will have within them objects
with cluster wide unique "keys" that can be referenced from any
location... I had a dream once that I had been programming everyday with
a full implementation of all these "new" "ideas" for the last four
years. Even funnier part of the dream is that the technology had been
around for ten. Could you believe that in my dream people who wanted to
use this novel technology were met with resistance. Thank god we don't
all live in my twisted dreams.
Ok. back to OO QBasic, got to get some real work done.
On Mon, 2003-11-10 at 06:36, bryan wrote:
> “Tapestry is an overlay network that sits at the application layer (on
> top of an Operating System). Deployed as a network connecting a set of
> machines, Tapestry allows any member node to route messages to any
> other node in the network, given a location and network independent
> name. Furthermore, Tapestry functions as a decentralized directory
> service for any objects residing on nodes in the network. A node in a
> Tapestry network can advertise or "publish" location information about
> an object it possesses. Any other Tapestry node can then act as a
> client, and send messages to this object, as long as it knew the
> object's unique identifier. These messages route through the overlay
> from node to node until they arrive at the node where the object is
> stored, such that the path taken is a small factor longer than the
> shortest path from the client node to the object's location.”
> Maybe I’m just weird but I was reading thru this and thinking, why
> does it always have to be java.
> Ah well….
More information about the erlang-questions