[Openslp-devel] Considering adding SuSE extensions to OpenSLP 2.0
Brought to you by:
jcalcote
From: John C. <joh...@gm...> - 2012-11-13 17:55:53
|
I'm currently adding the Suse patches (those that haven't made it in previously) to the repository in preparation for the 2.0 release. I started applying the smaller ones first - mostly security review patches - and then realized it would probably be better to add them in the same order they're specified in the suse rpm spec file to provide the best context for applying later patches in the list. (I would normally always apply them in order, but these patches were written for a different code base - 1.2 - so they have to be applied manually anyway.) Patch number 3 (in the 23 patch set) is the Suse extension patch. They've added multicast dns functionality to openSLP. http://en.wikipedia.org/wiki/Multicast_DNS My first reaction to this (a few years ago) was to reject it, but I'm rethinking it now - it might be a nice 2.0 feature (and Suse's been using it for years so it's well tested). Question: Is anyone out there opposed to OpenSLP gathering entries from, and pushing entries into, the mdns space? I don't want to add this if it's going to cause significant problems for SLP users. Also consider the possibility of making it both a compile-in option, and runtime-enabled via config options. John |