On 10/15/2012 04:40 PM, Nick Wagner wrote:
>
> I think this is great!
>
> Are there any other patches or fixes we want to get in before this
> deadline? Has anyone looked at Gavin Lambert's patch to the
> dynamically changing IP addresses?
>
I looked at it very briefly and it seems to me that it is not quite
'finished' yet:
* I guess that SLPDIncomingDeinit() will close all open connections,
which should only be done for 'disappearing' network interfaces.
* Also outgoing connections for 'disappearing' interfaces should be
closed and cleaned up.
* The net.slp.interfaces property seems to behave somewhat strange; it
can be used to specify which interfaces should be used, but afterwards
it will indicate the actually used interfaces. This will work fine for
the current 'one time configure' mechanism, but will probably have to be
fixed for a more 'dynamic' mechanism.
Since I'm not that much into the slpd_incoming/outgoing code, I may be
entirely wrong ;-)
My apologies to Gavin for not replying to you directly, but I intended
to do a more thorough review first...
Best regards,
Roel
>
> --Nick
>
>
> On Oct 12, 2012 11:16 AM, "Jim Marshall"
> <jim.marsh...@wbemsolutions.com
> <mailto:jim.marsh...@wbemsolutions.com>> wrote:
>
> Hi,
> WS would like to propose a release date of 10/26 for OpenSLP
> 2.0. I believe it has been a bit over a year since Beta 2 was
> released and we feel that it is important to get a 'stable'
> release out that people, and industry, can use and rely on.
> We have developed a set of tests which use the Java API (using
> JUnit) and the SLP daemon as well as some basic scripts which
> utilize the 'slptool' executable - for example registering,
> retrieving, modifying, , deregistering a service, checking
> attributes and their values. Additionally we have tested using the
> 2.0 code with the 1.x line of daemons and client. Additionally we
> would be willing to donate the test code to the open source so it
> can be used in the future. I believe we used the latest SVN trunk
> to test (1690).
>
> In line with a 10/26 release date we would propose a "code freeze"
> starting on 10/21 to allow for us to run our tests and to fix any
> issues that may be found.
>
> Lastly, if necessary, WS is willing to do the leg work of getting
> the release done.
>
> Does anyone have any objections?
>
>
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
>
>
> _______________________________________________
> Openslp-devel mailing list
> Openslp-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openslp-devel
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Openslp-devel mailing list
Openslp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openslp-devel
