2009/9/16 Peter Saint-Andre <[email protected]>: >> Agreed. The only reason I champion collection nodes as I do is that >> I don't know what "node as code" means. It might be better, but in the >> mean time the only solution I have is collection nodes. > > Ralph? ;-) >
I try to guess ;) Though I don't see a direct connection with collection nodes, this isa concept we are exploring thanks to Ralph's implementation in wokkel which allows implementing custom logic behind a node. At present we all think to pubsub nodes as simple dispatchers that follow rules defined by node configuration and affiliations, i.e. we publish an event and, by applying those rules, the event is delivered as it is to a set of subscribers, always to the same ones for any event. Things become more interesting when we can customize the behavior of a node by writing our code processing a publish or delete of an item, so that we can transform the item itself before delivering it, aggregate the events, implement our delivery policy (e.g. content based delivery, or things like delivering to just the highest priority online subscriber). Perhaps the possibility of doing content based delivery is something which is similar to collection nodes, but this would require to specify some selection options in the subscription. bye -- Fabio Forno, Ph.D. Bluendo srl http://www.bluendo.com jabber id: [email protected]
