That indeed takes away a large part of my worries
guess i'll have to test a little more with more implementations
and see how peacefully they work together.
Since most end-users don't actually know *anything* about
rendezvous i'd like to hide as much as i can. A generic solution
would be best (if we just all standarized on one implementation
but thats not very likely to happen i suppose)
--Ray
----- Original Message -----
From: "Scott Herscher" <email@hidden>
To: "Ray Molenkamp" <email@hidden>
Cc: <email@hidden>
Sent: Tuesday, July 13, 2004 12:25 AM
Subject: Re: Rendezvous on windows/.Net.
> Ray,
>
> I can't speak for all the Rendezvous implementations, however I'm the
> author of Howl and am somewhat familiar with Rendezvous For Windows by
> Apple. Typically, programs that are receiving multicast dns traffic on
> port 5353 turn on the reuse address option on the socket. Apple's code
> does this, and so does Howl. I'm fairly certain you'll find that most
> implementations will do the same. In so doing, multiple multicast dns
> implementations on the same machine can coexist peacefully.
> Inefficiently, but peacefully.
>
> Hope that helps,
>
> Scott
>
> On Jul 12, 2004, at 3:14 PM, Ray Molenkamp wrote:
>
> > Hi,
> >
> > For a commericial project i'm asked to use rendezvous on windows
> > now i wrote my own implementation using rawsockets in C# (not the
> > cleanest code but it works) but i'm a bit worried about the following:
> >
> > To recieve rendezvous traffic my application should bind to port 5353
> > to my knowledge only one application can bind to a port.
> >
> > I however have seen serveral other implementations of the rendezvous
> > protocol on windows there is:
> >
> > - Howl (http://www.porchdogsoft.com/products/howl/)
> > - msdnresponder by novell
> > (http://forge.novell.com/modules/xfmod/project/?mdnsresponder)
> > - Rendezvous for windows (techpreview) by apple
> > (http://developer.apple.com/macosx/rendezvous/index.html)
> > - Probably a bunch of other ones I don't know about.
> >
> > Now given the fact i have totally no control on what is or gets
> > installed on
> > the
> > end-user/customer's pc. How can i make sure i'm able to deliver
> > properly
> > working
> > software? is there a common way to deal with these things? Should i
> > *force*
> > my
> > customers to use my implementation and remove all other ones? or
> > should i go
> > through great lengths of effort to support any implementation I can
> > find?!
> >
> > In other words:
> >
> > Is it just me or is this really cool technology starting to look like
> > a real
> > big mess
> > on windows?
> >
> > --Ray Molenkamp
> > _______________________________________________
> > rendezvous mailing list | email@hidden
> > Help/Unsubscribe/Archives:
> > http://www.lists.apple.com/mailman/listinfo/rendezvous
> > Do not post admin requests to the list. They will be ignored.
_______________________________________________
rendezvous mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/rendezvous
Do not post admin requests to the list. They will be ignored.
