Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 6 Apr 2003 13:23:45 -0400
From: Craig Rodrigues <rodrigc@attbi.com>
To: Garrett Rooney <rooneg@electricjellyfish.net>
Cc: dev@apr.apache.org
Subject: Re: [PATCH] the beginnings of multicast support
Message-ID: <20030406172345.GA26409@attbi.com>
References: <DF9AA698-6840-11D7-BE59-000393CE23F4@electricjellyfish.net>
 <20030406155058.GA26064@attbi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030406155058.GA26064@attbi.com>
User-Agent: Mutt/1.4i

Hi,

The issues with multicast have to do with subscribing
to multicast groups and receiving certain datagrams.

The issues are summarized here:

http://www.dresystems.com/multicast.html

This may or may not affect your efforts to write a portable
API for multicast sockets, but it is worth noting.
-- 
Craig Rodrigues        
http://home.attbi.com/~rodrigc
rodrigc@attbi.com


On Sun, Apr 06, 2003 at 11:50:58AM -0400, Craig Rodrigues wrote:
> Hi,
> 
> There are issues with multicast...it is not as easy
> as just reading Stevens and doing the relevant setsockopt() calls.
> There are portability issues with multicast, especially
> with respect to IGMPv2 vs. IGMPv3 compliant behavior.
> 
> I will try to dig up some references on it.  In the mean time,
> you might want to look at libnet.  They have a portability
> layer for multicast sockets.  It is pretty close to what you have,
> but there is some additional stuff for other platforms (such as Windows)
> 
> http://www.packetfactory.net/projects/libnet/