Nick,
Given the insight inspired by your single question, I believe this change is
too big to take on right before a release. Additionally, it needs some
additional thought because it adds to the public interface defined by slp.h
- such changes should be voted on, not just accepted without critical
thought. Additionally, it adds a significant amount of new code. This can
destabilize the code base - again, not a good thing right before a release.
I think mdns enhancements are a good idea, but the way they work should be
discussed in the community, not just accepted without question just because
a particular linux distro's been using them for a while. I feel certain that
we can find a way to integrate mdns enhancements with both minimal and
well-considered changes to the public interface, and without causing
potential future problems in the way OpenSLP works within the framework of
the SLP standard.
I'll limit my changes to just relevant security fixes, and we'll take on the
mdns enhancement a bit more slowly for a future release. For now, I'll keep
my changes in a working patch set.
Thanks,
John
From: nwagner...@gmail.com [mailto:nwagner...@gmail.com] On Behalf Of Nick
Wagner
Sent: Wednesday, November 14, 2012 9:45 AM
To: John Calcote
Cc: OpenSLP Devel Mailing List; OpenSLP Users Mailing List
Subject: Re: [Openslp-devel] Considering adding SuSE extensions to OpenSLP
2.0
If it can be enabled at runtime or even compile time, I'd be ok with it.
How would attributes fit into it, if at all?
--Nick
On Tue, Nov 13, 2012 at 11:55 AM, John Calcote <john.calc...@gmail.com>
wrote:
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
----------------------------------------------------------------------------
--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
Openslp-devel mailing list
openslp-de...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openslp-devel
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
Openslp-users mailing list
Openslp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openslp-users
