All things related to multicast

[Hoerdt Mickael <>]

Well, your function should be then called join_dgram_SSM, which I 
suppose will use UDP as a transport protocol. Maybe I am wrong but 
that's mean that you will bind your socket to
a user-defined port or a automatically choosen by the system ( in 
addition to the SSM address) ?

If this is the case, that means that for your application : you have to 
know the bind port
by some way (getsockname or something), I think more general to separate 
binding from
SSM joining, because I might write some ICMP over SSM protocol or something.

Maybe it's a detail but... open_SSM != open_UDP_SSM.

Hoerdt Mickael

Stig Venaas a écrit :

> On Wed, Nov 17, 2004 at 10:15:20AM +0100, Hoerdt Mickael wrote:
>  
>
> > Hi Alan,
> >
> > You shouln't bind your socket before joining the SSM channel I think, 
> > try to bind it after or better,
> > try to bind it outside of the openSSM function : joining an SSM channel 
> > is an IP operation, which
> > is not related to socket binding (ususally related to transport operation).
> >    
>
> Are you sure? I'm not aware of any restrictions, but interested to know
> if any operating systems have any.
>
> To me it seems more appropriate to bind before joining so that you're
> prepared to receive packets that may arrive immediately after joining.
>
> I guess this is mainly a matter of style and taste.
>
> Stig
>