#    Copyright (c) 1999 University of Southern California.
#    All rights reserved.                                            
#                                                                   
#    Redistribution and use in source and binary forms are permitted
#    provided that the above copyright notice and this paragraph are
#    duplicated in all such forms and that any documentation, advertising
#    materials, and other materials related to such distribution and use
#    acknowledge that the software was developed by the University of
#    Southern California, Information Sciences Institute.  The name of the
#    University may not be used to endorse or promote products derived from
#    this software without specific prior written permission.
#    
#    THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED
#    WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
#    MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

LSAM CHANNEL MULTICAST
======================
LSAM Authors: Lars Eggert, Anne Hutton, Amy S. Hughes
$Revision: 1.9 $ ($Date: 1999/05/12 17:30:24 $)
More information: http://www.isi.edu/lsam/


Introduction
------------

Channels are created from the channel_status form at
http://your_server/cgi-bin/lsam/channel_status.pl

The announcements for these channels are made to other web servers and proxies
via a well-known multicast announcement channel. The current test multicast
address for channel announcements is 224.6.3.1 and the port 8999. The channels
can be created by an administrator unaided or aided by the log analysis
process, i.e. they can be created and destroyed by manual control
(http://your_server/cgi-bin/lsam/LA_add_chanel.pl which is called from the
channel_status page) or can be managed within LSAM by its automated join/leave
mechanism.

The current system always unicasts a response to a request, and always
multicasts a push for requests that are members of any current channel.

It is possible that a response can match the URL prefix of more than one
currently active channel; in this case, the response is pushed ONLY on the
channel with the "longest prefix" match.