<quote> > >- multicast can only be done within the same subnet, while this is not true > > for the database connection. So, if you run 2 mmbase's on the same > > database, </quote>
This is not true. even with ipv4 it's possible to tunnel multicast. but it's really a lowlever operation. <quote> > > OK, but creating something with for instance RMI > (TCP based) would need more resources... Since multicast only happens at editing, peformance should not easily be a problem. I think that even if you set it up with one Thread it should easily be able to handle quite a lot of edits. And furthermore a delay of a few seconds does not matter, do it can simply queue if a 'burst' of invalidation requests comes in, and handle them one-by-one. </quote> When speaking in a more general manner it's quite likey that next to the current registation method (push) a polling method is required. That method must be able to answer questions like "what nodes changed the last day" in order for example to keep caches up to date. an other reason for making it possible to pull , is the nature of the web , where the client makes requests and the servers answers(and not the server deciding to push content to the client). doesnt' it sound like jave messaging ? greeting, Keesj who became dad 15-04-2004 http://www.keesj.dds.nl/sem.jpg
<<winmail.dat>>
