Re: [liblo] How to set SO_REUSEADDR for broadcast?

I'm okay with it if it seems to work for you.

Steve


On Mon, Feb 16, 2009 at 4:41 PM, Mike Wozniewski <mi...@mi...> wrote:
> Hi Steve,
>
> I'm back on the SO_REUSEPORT issue, since multicast is not working on
> OSX for multiple processes listening on the same port. Note: works in Linux.
>
> So if possible, can we make a change to src/server.c ??
>
> Around line 317, where SO_REUSEADDR is set, can we also set SO_REUSEPORT
> for platforms that support it? Something like:
>
> #ifdef SO_REUSEPORT
>    setsockopt(s->socket,SOL_SOCKET,SO_REUSEPORT,&yes,sizeof(yes));
> #endif
>
> Let me know if you think this will cause any problems, or if you want an
> official patch.
>
> Thanks in advance,
> -Mike
>
>
>
> Stephen Sinclair wrote:
>> On Thu, Feb 12, 2009 at 9:15 PM, Mike Wozniewski <mi...@mi...> wrote:
>>
>>> Hey Steve,
>>>
>>> Yeah, it seems like some machines here like SO_REUSEPORT, and some don't :(
>>>
>>> I'm finding that using broadcast for these types of things is really
>>> starting to be a pain, so I think I'm going to ditch it and change
>>> everything to multicast. Then I think SO_REUSEADDR is enough.
>>>
>>> So sorry, no sample code to give you.
>>>
>>
>> Cool, well I was going to suggest that, (I think maybe someone
>> suggested it previously), but it'd good to make the broadcast
>> implementation more robust.  These things just require so much testing
>> in many different environments however, it does become difficult to
>> find and solve these kinds of problems.
>>
>> For what it's worth, I've been using OSC-multicast with success,
>> though not necessarily always with the liblo implementation.  (Often
>> with the Max/MSP mxj objects.)  Please shout if you have trouble with
>> it, it hasn't had much testing.
>>
>>
>>
>>> However, I did write some simple Pd objects that might be of interest
>>> (much better than sendOSC and dumpOSC). You can find them here:
>>> http://www.cim.mcgill.ca/sresvn/audioscape/audioscape_resources/pdworks/src/OSCrxtx/
>>>
>>> The Makefile refers to the global 'pdworks' Makefile, so for ease of
>>> compilation, I'd suggest checking out the whole pdworks folder.
>>>
>>
>> Cool!
>> Have you posted about that on the Pd list?  They might be interested
>> to stick it in the Pd externals repository, or if not maybe we could
>> include it with LibLo.  (Well, I don't want to put all sorts of things
>> in there, but we've got oscsend and oscdump in there now, adding more
>> bindings might be interesting.)
>>
>>
>> Steve
>>
>> ------------------------------------------------------------------------------
>> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
>> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
>> -Strategies to boost innovation and cut costs with open source participation
>> -Receive a $600 discount off the registration fee with the source code: SFAD
>> http://p.sf.net/sfu/XcvMzF8H
>> _______________________________________________
>> liblo-devel mailing list
>> lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>>
>>
>
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>