On Thu, 7 Mar 1996, Brian Kelly wrote:
> Scaleability: The remote server update mechanism claims to scale well.
> In fact, since it is a broadcast mechanism, in the sense that all
> servers are informed of all updates, the total additional message
> traffic required scales proportionally to the number of servers. The
> forward referencing approach scales proportionally to the number of
> outward links held by an object, a much smaller figure than the number
> of servers.
What about if the scheme used a set of pruning multicast groups rather than
(effectively) a token passing ring so that the messages concerning a
particular server only went out to machines that were actually interested
in it? Multicast using RFC1112 compliant implementations ensures that the
bandwidth usage is minimised as update packets would only be copied at
points in the topology where they actually do have to go down different
links. Much effort has been made in the MBONE community to ensure an
efficient multicast routing topology and this could be a good way for the
Web to leverage some use out of the effort.
Tatty bye,
Jim'll
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Jon "Jim'll" Knight, Researcher, Sysop and General Dogsbody, Dept. Computer
Studies, Loughborough University of Technology, Leics., ENGLAND. LE11 3TU.
* I've found I now dream in Perl. More worryingly, I enjoy those dreams. *
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|