ah,
ok my misunderstanding then, I see your point, fair enough.
for the record, all interested parties in javaspaces can subscribe for
events from matching items in the space, and all will receive them.
all entities can also read that entity too, just like pubsub
notification+pull. Gigaspaces happens to support pushing dynamic script
tasks which I guess I was thinking was something like node as code when
combined with the space, but I think you are correct. this is quite
different.
Cheers
Waqas Hussain wrote:
On Thu, Dec 3, 2009 at 4:37 AM, Jason Eacott <[email protected]
<mailto:[email protected]>> wrote:
node as code sounds a LOT like a javaspaces to me, I like the idea
but if thats what you want, why not just use openspaces? or at least
something akin to the javaspace api?
It isn't like javaspaces. I suppose you could stretch javaspaces to map
to pubsub or pubsub to map to javaspaces, but they are quite different.
I'd say javaspaces are loosely similar to pubsub queueing.
Node as code is completely different. AFAIK, in javaspaces an item is
published to a 'space', which normally gets sent to any one consumer.
Node as code means the node behavior may be customized (filtering,
transformations, etc) via custom code. The node may not even exist until
someone subscribes.
--
Waqas Hussain
