On 11/10/2007, Bruce Snyder <[EMAIL PROTECTED]> wrote: > On 10/11/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > > So your snippet would actually solve the heartbeat problem. But I'm > > not sure we can send the whole data at each heartbeat. I guess it > > depends how bit this data is, but if we have lots of services in the > > OSGi registry, it may not be very scalable. So we would have to > > default to send only updates or find another mechanism to send the > > data (the heartbeat could just contain the url of our container, and > > the data would be retrieved by another mechanism). > > How about just sending the URL and a flag stating that there is an > update? If one of the other servers wants the update, then they can > poll that server's URL and a known topic for the actual data updates.
Great idea -- James ------- http://macstrac.blogspot.com/ Open Source SOA http://open.iona.com
