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.
