Re: tmdns implementation as a deamon

Robin Perkins <[email protected]> Wed, 28 Jul 2004 23:00:46 +0930
Newsgroups gmane.network.zeroconf.workers
Message-ID <[email protected]>
So long as you are building a "Larger Work" you are free to use 
whatever licence you like with the APSL api. The APSL v2 has been 
approved by the FSF - the main difference between the APSL and the GPL 
is that the APSL requires you to release changes to your software - 
with the GPL you only have to release if you release. This licence 
issue is no different to the apache licence and the GPL.

Also as far as I can tell the posix port is feature complete (it uses 
the same source files as the Mac version!) and it does run as a daemon 
(I have run it myself) but don't take my word for it - download it 
yourself and see.

http://developer.apple.com/darwin/projects/rendezvous/
(you will likely want the CVS version)

Rob

On 28/07/2004, at 10:40 PM, Vincent Hamm wrote:

> It's a licence problem.
> As far as I know, the licence apple used isn't GPL compatible. And I'm
> not quite enclined to start working on such an api if there is licence
> problemes.
> Also, the posix port is partial and doesn't exactly run as a deamon (I 
> think).
>
> Vincent
>
> On Wed, 28 Jul 2004 22:27:10 +0930, Robin Perkins
> <[email protected]> wrote:
>> Perhaps you might like to consider looking at Apple's implementation 
>> of
>> mdns - there is a port available for posix (which includes Linux)  as
>> well as Windows and of course Mac OS.
>>
>> It has been released under an open source license and could well be
>> considered to be the 'standard' setting implementation.
>>
>> Rob
>>
>>
>>
>> On 28/07/2004, at 7:15 PM, Vincent Hamm wrote:
>>
>>> Hi,
>>>
>>> I've been investigating mDNS implementations recently and I'm mainly
>>> focused on service discovery.
>>>
>>> I've tried tmdns which seems the only real deamon linux 
>>> implementation
>>> of mDNS and I ran into a bit of trouble. It seems to fail to open the
>>> multi-cast socket:
>>>
>>> Jul 28 10:01:33 belgarath tmdns[29971]: can not bind to device : No
>>> such device
>>> Jul 28 10:01:33 belgarath tmdns[29971]: Could not bind to port :
>>> Address already in use
>>> Jul 28 10:01:33 belgarath tmdns[29971]: can not open sender socket 
>>> for
>>> eth0/224.0.0.251#5353 : Address already in use
>>>
>>> Is there any kernel / firewall requirements regarding the use of 
>>> tmdns
>>> (I'm not used to multicasting) ?
>>>
>>> My other question deals with service discovery. Is there any plan
>>> regarding the possibility of having user programs connecting to tmdns
>>> to request the advertisement of a service not defined in 
>>> tmdns.service
>>> ?
>>>
>>> Anyway, good work so far. Tmdns seems to approach the groundwork I 
>>> was
>>> looking for to perform real service discovery under linux.
>>>
>>> Vincent Hamm
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.Net email is sponsored by BEA Weblogic Workshop
>>> FREE Java Enterprise J2EE developer tools!
>>> Get your free copy of BEA WebLogic Workshop 8.1 today.
>>> http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
>>> _______________________________________________
>>> zeroconf-workers mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/zeroconf-workers
>>>
>>
>>
>



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click