openslp-announce — OpenSLP announcements

[Openslp-announce] OpenSLP has moved to github!

[John C. <joh...@gm...>]

*General Announcement*

The OpenSLP project has moved to github

Link: https://github.com/openslp-org/openslp

I've migrated the entire project history from the existing sf.net mercurial
repository to the new github.com git repository.

The issue board has also officially moved to the github project site and I
will be migrating top issues from SF.net to the github issue board over the
coming weeks.

Currently, the sf.net project has a redirect badge at the top of the
summary page that redirects to the github project, along with a note in the
summary text that indicates the move.

Finally, the openslp git project exists (as you can see from the url above)
under the openslp-org organization. I'm currently the only member of the
organization. If anyone is interested in joining, please email me on the
openslp-devel mailing list at ope...@li... (still
hosted by sf.net at this time).

I hope this move encourages contributors to open pull requests as this
seems to be the modern way of submitting patches to open source projects.

Thanks,

John Calcote
OpenSLP.org

[Openslp-announce] OpenSLP 2.0.0 Released!

[John C. <joh...@gm...>]

We're excited to announce the long-awaited release of OpenSLP 2.0.0. 

 

Sourceforge.net has been updated with new 2.0.0 download packages (tar.gz
source and doxygen tarballs), as well as Windows x86 and x64 msi installer
packages. 

 

http://sourceforge.net/projects/openslp

 

Enjoy!

[Openslp-announce] OpenSLP 2.0 beta2 64-bit Windows installer and doxygen bundle now available

[John C. <joh...@gm...>]

UPDATED

 

-        The OpenSLP website download page has been updated to reflect the
2.0 beta2 release that occurred last month. The download page now refers to
the available 2.0 beta2 downloads (rather than the older beta1 files).

 

NEW

 

-        A 64-bit OpenSLP 2.0 beta2 MSI installer has been added to the list
of packages available for download on the OpenSLP website.

    http://openslp.org/download.html
    http://sourceforge.net/projects/openslp/files

[Note that the default download package for Windows is the x86 MSI
installer, so go to the Download page at openslp.org to get the x64
installer, or else drill down into the files list at the project page on
sf.net to access it.]

-        An updated doxygen bundle (tar.gz) has also been added to the 2.0.0
beta2 download files directory, as well as an access link on the openslp.org
download page.

 

Enjoy!

John

[Openslp-announce] OpenSLP 2.0 beta 2 windows installer (x86) available for download

[John C. <joh...@gm...>]

I've just released an x86 MSI installer for OpenSLP 2.0 beta 2 for Windows.
Please download from the OpenSLP project page on sourceforge.net.

 

http://www.sourceforge.net/projects/openslp

 

Regards,

John

[Openslp-announce] OpenSLP 2.0 beta 2 has been released!

[John C. <joh...@gm...>]

We're happy to announce the beta 2 release of openslp 2.0.

Changes primarily include bug fixes to the beta 1 release.

Currently, the only format is a source tarball (tar.gz), but a Windows
MSI is forthcoming shortly.

Our website has been updated recently to reflect the latest information
on OpenSLP and SLP in general.

   http://openslp.org

Download beta 2 and give it a try.

   http://sourceforge.net/projects/openslp

John

[Openslp-announce] OpenSLP 2.0 Beta 2 Binaries (w32.msi, rpm, deb, etc)

[John C. <joh...@gm...>]

Hi all,

Just a short note to let you know about various binaries available for 
the OpenSLP 2.0 beta 2 release:

1. I've just uploaded a Win32 MSI package to the sf.net project site:

http://www.sourceforge.net/projects/openslp

2. I've been maintaining RPM and Debian packages during ongoing 
development on the OpenSuSE Build Service (OBS) at 
http://build.opensuse.org. To access the binaries, just go to this 
persistent search URL at download.opensuse.org:

http://software.opensuse.org/search?baseproject=ALL&p=1&q=openslp

Enjoy!
John

[Openslp-announce] OpenSLP 2.0 beta 1 released!

[John C. <joh...@gm...>]

I'm happy to announce that the openslp 2.0 code base is ready for beta. 
We've tested all main-line functionality on Linux, Solaris and AIX. It 
appears to work fine. Please give it a try and let us know.

http://www.sourceforge.net/projects/openslp

Enjoy!
John

[Openslp-announce] Two new developers on OpenSLP!

[John C. <jca...@no...>]

Everyone,

I'd like to welcome two new developers to the OpenSLP project: Matthew
Hird and Stephen Edwards, both of Thales Underwater Systems in the UK.
Matt and Stephen have been using OpenSLP for service advertising in the
work they've been doing for Thales.  Both are expert C and Java
programmers. They'll be focusing on improving the slpd daemon and the
Java API - great news since we've not had a lot of improvement in the
Java code for a while now.

Welcome Matt and Stephen!

[Openslp-announce] www.openslp.org is back on line

[John C. <jca...@no...>]

Everyone,

The OpenSLP web site is back up on www.openslp.org.

Novell is now officially sponsoring the project and hosting the DNS IN
A and CNAME records for the vhost references to openslp.sf.net. I think
we can expect the site to be operational for the foreseeable future.

Sorry for the inconvenience.

John

[Openslp-announce] Welcome to Jim Davis

[John C. <jca...@no...>]

Everyone,
 
The OpenSLP project is pleased to welcome Jim Davis as a developer. Jim
is CTO of WBEM solutions, and the chair of the DMTF WBEM Infrastructure
and Protocol (WIP) working group. WIP uses SLP as one advertising
mechanism, and Jim has volunteered some of his company time to make
OpenSLP a better implementation of the SLP protocol.
 
Jim will be focusing at first on the Java implementation, and will also
help with the C code base.
 
John Calcote
Project Admin, OpenSLP
Novell, Inc.
 

[Openslp-announce] OpenSLP 2.0.0 alpha 1 released!

[John C. <jca...@no...>]

OpenSLP 2.0.0 alpha 1 has been released in source format (tar.gz).
Please try it out and let us know what's wrong. :)
 
John

[Openslp-announce] OpenSLP project migrates from cvs to subversion

[John C. <jca...@no...>]

The openslp code base has been successfully migrated to subversion on
sourceforge.net. Please refer to the Subversion link at the top of the
project page at http://www.sf.net/projects/openslp to find out how to
access the new repository. The repository is browsable through this
link, just as was the CVS repository.
 
SourceForge offers a complete project migration, so the entire history
of the openslp CVS project is captured in the new SVN repository under
the branches and tags directories. The existing CVS HEAD revision is now
found under the SVN "trunk" directory. Please note, if you are not
familiar with subversion, you should use the following URL to checkout
the HEAD (trunk) branch of the code:
 
     https://svn.sourceforge.net/svnroot/openslp/trunk
 
If you leave "trunk" off the end of the URL, you will get THOUSANDS AND
THOUSANDS of files in your work area - one for each file in the
repository in each branch or tag ever created while under CVS. Since
openslp is a fairly long-standing project, this means a LOT of files.
SVN repositories manage this many files effectively by using links to
the trunk line, which means there aren't really that many files, but
work areas will have separate files for each link in the repository.
 
You will, of course, need a subversion client. I use both TortoiseSVN
(Windows file system explorer plugin) and SmartSVN (portable java gui -
works identically on Windows and Linux/Unix). Both are very clean client
implementation, and both work very well. SmartSVN is a bit more
functional, but unless you really get into it, you probably won't notice
the difference. You may, of course, use the subversion command line
client, which is always 100% functional, and is generally installed by
default in most Linux distros (usually installed with the "development"
packages).
 
The subversion specification was designed by folks at Tigris
(http://subversion.tigris.org) who worked on the original design of CVS.
Subversion was designed to ultimately replace CVS, fixing its inherent
drawbacks (CVS has no directory structure management, for instance).
Most new sourceforge projects are starting up with subversion
repositories, and many existing projects are migrating.
 
IMPORTANT: 
 
Please don't continue to check changes into the CVS repository. Even
though the CVS link has been removed from the openslp project's menu,
you will still be able to access the old CVS repository using previous
URL's and CVS commands. Your changes to the CVS repository will not
appear in any new releases.
 
John
 
-----
John Calcote (jca...@no...)
Sr. Software Engineeer
Novell, Inc.

[Openslp-announce] www.openslp.org is back up

[John C. <jca...@no...>]

Okay everyone,
 
I've repurchased the openslp.org domain for the next 5 years. It was
cheaper than I first realized, so I went ahead with it. Sorry for the
pointless noise on this announcement list, but we're back up and running
at the usual place: 
 
     http://www.openslp.org
 
John
 
 
 
 
-----
John Calcote (jca...@no...)
Sr. Software Engineeer
Novell, Inc.

[Openslp-announce] Re: Open SLP website

[John C. <jca...@no...>]

Everyone - until further notice, the openslp home page dns name has been
changed to the default home page URL sponsored by sourceforge.net.
 
The old dns name was http://www.openslp.org. 
 
The new name (until further notice) will be
http://openslp.sourceforge.net.
 
Caldera had purchased this name from a parasite company in Herndon, VA.
I can't afford to renew on my salary at 12 bucks a month. I'm going to
try to wait them out - perhaps they'll release it back to the public,
and then I can purchase it back for 20 bucks a year from IANA.
 
Thanks for your patience,
John Calcote
Project Admin
OpenSLP

>>> "Matt" <gin...@us...> 2/23/2006 6:43:52 am
>>>

Message body follows:

Hi, 

did you know that the domain for the OpenSLP website has
expired and you can no longer access it? 

Also, do you know when you are likely to release v2.0?

cheers,

Matt

--
This message has been sent to you, a registered SourceForge.net user,
by another site user, through the SourceForge.net site.  This message
has been delivered to your SourceForge.net mail alias.  You may reply
to this message using the "Reply" feature of your email client, or
using the messaging facility of SourceForge.net at:
https://sourceforge.net/sendmessage.php?touser=1329480

[Openslp-announce] welcome...

[John C. <jca...@no...>]

Everyone,
 
I'd like to welcome two new developers to the sf.net openslp project:
 
- Michael Schroeder of SuSE in Germany
- Peter Marschall, also in Germany
 
Both of these gentlemen have contributed several very significant bug
fixes and patches already in the last few months, and subsequently, I've
asked them if they would like check-in rights on the openslp project.
They've both graciously accepted. Michael was granted developer status a
couple of weeks ago, and as of today, Peter has developer status also.
As such, they should be considered resources on this project for
fielding new feature ideas, and I'm sure we'll hear more from them
occasionally on these mailing lists within that capacity.
 
To update our position with the 1.2.x stable line, a new release is
forthcoming shortly which should fix a number of bugs, including a
complete overhaul of the build system. Autotools have been brought up to
current standards, and I'm trying out the sourceforge compile farm to
ensure that at least a few basic platforms will build.
 
Thanks,
John 
 
 
-----
John Calcote (jca...@no...)
Sr. Software Engineeer
Novell, Inc.

[Openslp-announce] OpenSLP moves forward once again

[John C. <jca...@no...>]

Everyone,
 
I apologize for the lack of traffic on this list. I know it's been sort
of quiet lately. I've recently taken ownership of this project. I wanted
to make a public statement concerning the future direction of the
OpenSLP project. I've spent the last couple of weeks familiarizing
myself with the current implementation, and I now feel more comfortable
making an agenda for completion of partially implemented or missing
features, and for performance enhancement.
 
The following features are missing, or could be optimized:
 
1. Asynchronous UA operation. This is currently only partially
implemented. Mainly what's missing is threading primitives, and the
correct management of client library threads. It's really fairly trivial
at this point, but was never added for a couple of reasons that I can
determine. First, the entire code base is currently single-threaded
(even slpd). There's nothing wrong with this. A good single-threaded
implementation can be faster than a multi-threaded implementation, if
done correctly. Threading adds SMP scalability, not speed. I would like
to add threading to the UA for asynchronous API operation.
 
2. Which brings me to my next point - SMP scalablity for slpd. I don't
want to add lots of threads to the server. Even in large installations,
the traffic just doesn't warrant adding threading on a massive scale.
However, I do believe performance would be benefited by multi-threading
the server, specifically for DA's, which do receive more requests than
SA's. Adding threading in both the UA and the SA/DA server requires the
creation of a small set of threading and synchronization primitives,
including threads, mutexs and condition variables, at the very least. I
need to consider options that are already available, of course, but one
concern is that up to this point, the OpenSLP source base has been
entirely self-contained. Maintaining this self-containment has to be
considered in any decision regarding which threading library to use.
 
3. Remote database configuration. I'd like to add _configurable_ LDAP
support to the DA. That is, I'd like the storage of directory
information to be configured to be internal or external via OpenLDAP
based on administrator policy. Directories are somewhat commodity these
days, and nearly every installation site for OpenSLP also has a
corporate directory available. Another configurable storage option might
be an ODBC or other standard database interface for storing directory
information in a more optimal format. These features would lend
themselves to persistent service registry, as well, which was never
fully completed.
 
4. It's time for a refactor. There are many places in the code base
where it's pretty clear that code was just copied wholesale from one
routine to another, because it was convenient and fast. Refactoring
means moving code into common routines, to improve maintainability, and
reduce defects.
 
5. After a while, the source code of an open source project with
multiple developers tends to take on a "wild-hair" sort of look. That
is, the formatting from one source file to another is disjoint and of
different styles. While the OpenSLP project is not too bad in this
respect, given the amount of time it has been alive, it could use a
little reformatting to get it back to a smooth source base. To this end,
I've purchased a license for a share-ware product called
SourceFormatterX, which is really cool. I'll be setting it up to restyle
the code base to match most of the style that Matt Peterson used in the
original source code a few years ago. These changes will affect many
source files at once, and I expect to do this major formatting change
soon.
 
I'll be sending out more notes like this occasionally to announce other
areas on which I intend to spend time.
 
Thanks for your support. Please feel free to let me know of features
you'd like to see. I'm monitoring these lists, and I want the traffic
logged and publically visible, so it's probably most appropriate to use
the openslp project's developer mailing list at
ope...@li..., however you are welcome to email me
directly, as well at jca...@no.... 
 
John Calcote
Novell, Inc.
 

[Openslp-announce] That time has come...

[Matt P. <mpe...@ce...>]

Greetings everyone,

That time has come when I've realized that I will no longer be able to spend 
as much time on SLP as I would like.  

I have left SCO as part of a technology purchase by a company called Center7.  
Incedentally, Center7 also purchased the openslp.org and openslp.com domains 
as well as the OpenSLP copyright.  

My new role at Center7 is such that I have become extremely busy working on a 
project that is not related to SLP so I have a very difficult time finding 
time to work on OpenSLP.

Therefore, the time has come for me to hand solicit help from a new project 
maintainer.  Having maintence control of OpenSLP is really quite valueable 
for anyone who has built OpenSLP into a commercial offering -- at least it 
has been for me.  

Though I'd expect the new maintainer to be concious of the requests from the 
community and especially careful to follow IETF standard, they will certainly 
be welcome to make releases and apply patches that are suited to their needs.  
After all there should be some reward for those who spend time maintaining 
the project.

If you are interested in becoming the new OpenSLP project maintainer.  Please 
send email to me at:

   mpe...@ce...
   
Thanks,

--
Matt

[Openslp-announce] SLP API for Java

[Matt P. <mpe...@ce...>]

Hi,

Thanks to  Dave Cooper and Solars Corporation, the OpenSLP project is abl=
e to=20
offer a pure  Java implementation of the SLP API.   has been posted on th=
e=20
OpenSLP web site. =20

For more information see:

http://www.openslp.org/download.html#java

[Openslp-announce] IMPORTANT: Openslp does not work on RH8.0

[Matt P. <ma...@sc...>]

OK.  I've finally figured out what is going on here:

It turns out that the newer versions of GCC use strict aliasing as part o=
f the=20
-O3 optimizations.  The ToUINTxx() macros are not "alias safe".  In other=
=20
words, they assume that differing pointer types can point to the same mem=
ory=20
location.  There is a simple work around that is now checked into CVS and=
=20
will be available in the next release of OpenSLP 1.0.11.  The fix involve=
s a=20
changing the ToUINTxx() macros to simple inline functions.

For those of you still compiling OpenSLP 1.0.10 you MUST modify CFLAGS to=
=20
include the -fno-strict-aliasing flag or compile without -O3.


On Thursday 13 February 2003 01:53 am, Christoph Bartoschek wrote:
> Hi,
>
> your attached programm was incomplete in regard to our problem. I've
> modified it such that it shows the FAILURE on my machine, with an outpu=
t of
>
> FAILURE: Your machine is busted
> 0x0
> 0x0
> 0x0
> 0x0
> 0xbb
> 0x0
> 0x2
> 0xaa
> 0xbb
> 0x0
>
> it is neccessary that you compile it with
> gcc -O3 htons_test.c
> because optimized code uses a macro htons while unoptimized code calls =
a
> function. The resulting binary fails on two other machines. A Athlon an=
d a
> Celeron. You should compile the program with -E to see the difference
> between RH8.0 and other machines.
>
> My machine is a
>
> processor       : 0
> vendor_id       : GenuineIntel
> cpu family      : 15
> model           : 2
> model name      : Intel(R) Pentium(R) 4 CPU 2.40GHz
> stepping        : 4
> cpu MHz         : 2405.513
> cache size      : 512 KB
> fdiv_bug        : no
> hlt_bug         : no
> f00f_bug        : no
> coma_bug        : no
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 2
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge =
mca
> cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
> bogomips        : 4784.26
>
>
> The same error occurs in RH 8.1beta2. Therefore I conclude there is a e=
rror
> in the glibc.
>
> BTW, you should always include the header files you need.
>
> Am Donnerstag, 13. Februar 2003 01:03 schrieben Sie:
> > Christoph,
> >
> > I have checked this out on a Redhat 8.0 machine in our lab.
> >
> > $ cat /proc/cpuinfo
> >
> > processor       : 0
> > vendor_id       : GenuineIntel
> > cpu family      : 6
> > model           : 8
> > model name      : Pentium III (Coppermine)
> > stepping        : 3
> > cpu MHz         : 937.597
> > cache size      : 256 KB
> > Physical processor ID   : 1631139384
> > Number of siblings      : 1
> > fdiv_bug        : no
> > hlt_bug         : no
> > f00f_bug        : no
> > coma_bug        : no
> > fpu             : yes
> > fpu_exception   : yes
> > cpuid level     : 2
> > wp              : yes
> > flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pg=
e
> > mca cmov pat pse36 mmx fxsr sse
> > bogomips        : 1859.14
> >
> > I do not see any problems.  I have attached a very short program that
> > runs a quick test.  If you can verify that the attached source identi=
fies
> > the problem on your pentium 4 then I will send it to RedHat as part o=
f a
> > bug report against RH8.0
> >
> > Thanks,
> >
> > Matt

[Openslp-announce] Development release of OpenSLP 1.1.3

[Matt P. <ma...@sc...>]

Hi,

It is about time that I made another development release.  The following is a 
list of the major changes:

* The main new feature is the very good DHCP and win32 porting work that has
  been contributed jca...@no...
* Preliminary integration of new filter and predicate code based on work done
   by Mike Day. Code should be operational by next release.

The source tarball can be downloaded from the following URL:

http://www.openslp.org/download.html#development

--
Matt Peterson

[Openslp-announce] OpenSLP 1.0.10 Released

[Matthew P. <ma...@sc...>]

The latest stable version of OpenSLP is 1.0.10.  OpenSLP-1.0.10 contains 
a few minor bug fixes that some OpenSLP users will be interested in.  

* Fixed SA->DA registration logic that excluded some mortal  
  registrations.
* Fixed aging problem that aged out static registrations
* SLPDeReg() fix from Matthew Layton
* Fixed win32 project files so that ENABLE_PREDICATES is defined
* Commited patch from Roger Tawa that fixes a segfault generated by a
  freed but unlinked SLPDSocket.
* Commited patch from Vinupama Godavarthi the makes net.slp.multicastIF
  work


Download the latest from:

   http://openslp.org/download.html

[Openslp-announce] ENABLE_PREDICATES not defined in default MSVC project files

[Matt P. <ma...@sc...>]

Hi,

I reciently found out that there is an error in the MSVC project files=20
that causes predicate functionality to be ommited from win32 builds of=20
OpenSLP.  The problem is that we did not update the MSVC project files=20
when we updated the autoconf/automake build system used on *nix=20
platforms. =20

The old #define USE_PREDICATES was changed to ENABLE_PREDICATES in the=20
autoconf/automake build system and in the code, but the change was=20
never made to the MSVC project files.

If you are building OpenSLP using MSVC on win32, you will need to change=20
the project settings so that ENABLE_PREDICATES is defined instead of=20
USE_PREDICATES.  To do this, select the Project -> Settings menu option=20
(or use the alt-f7 hotkey).  Select "slpd" in the left panel and set=20
the "Settings For" spinner to "All Configurations".  "In the=20
Preprocessor definitions" replace the string "USE_PREDICATES" to=20
"ENABLE_PREDICATES".  After making this change, do a "rebuild all" on=20
slpd.

--=20
Matt Peterson
Sr. Software Engineer
The SCO Group (formerly Caldera, Inc)

[Openslp-announce] OpenSLP 1.0.9a released

[Matthew P. <ma...@ca...>]

Hi,

As indicated by the previous email to the list, OpenSLP 1.0.9 as mistakenly 
released with an very innocent but problematic bug.  The fix was extremely 
simple, but still probably warrents a new release.

ALL users should download 1.0.9a from the following link:

   http://openslp.org/download.html

Again, sorry for any inconvenience.

--
Matt Peterson
Sr. Software Engineer
Caldera, Inc

[Openslp-announce] OpenSLP 1.0.9 Released

[<ma...@ca...>]

OpenSLP-1.0.9 contains a few minor bug fixes that some OpenSLP users will=
 be=20
interested in. Most of all, OpenSLP 1.0.9 probably represents the last=20
official release of the 1.0.x branch.  Subsequent releases will only be m=
ade=20
if serious bug fixes are needed.  Otherwise, all changes will be made to =
the=20
development 1.1.x branch.

Those that are investigating OpenSLP as part of a development or porting=20
project should look at the 1.1.x development releases.  This is where the=
=20
development action will be.  Those that are deploying OpenSLP in producti=
on=20
systems should continue to look at OpenSLP 1.0.9 until the 1.1.x code bec=
omes=20
stable enought for production use.

Get the latest at http://openslp.org/download.html

--=20
Matt Peterson
Sr. Software Engineer
Caldera, Inc

[Openslp-announce] openslp-1.0.8 is a broken build -- patch or download openslp-1.0.8a

[Matt P. <ma...@ca...>]

Ayman,

Thanks for the information.  It has helped me to find a bug that some how 
managed to get into 1.0.8.  I'm not sure if it was a inadvertant cut and 
paste mistake or if it was legitimate.  Regardless, there is a line in 
slpd_incoming.c that should not be there.  I am embarrassed that this slipped 
past validation testing.  OpenSLP 1.0.8 never should have been released with 
line 99 of slpd_incoming.c.

/*-------------------------------------------------------------------------*/
void IncomingDatagramRead(SLPList* socklist, SLPDSocket* sock)
/*-------------------------------------------------------------------------*/
{
    int                 bytesread;
    int                 bytestowrite;
    int                 byteswritten;
    int                 peeraddrlen = sizeof(struct sockaddr_in);

    bytesread = recvfrom(sock->fd,
                         sock->recvbuf->start,
                         SLP_MAX_DATAGRAM_SIZE,
                         0,
                         (struct sockaddr *) &(sock->peeraddr),
                         &peeraddrlen);
    if (bytesread > 0)
    {
        sock->recvbuf->end = sock->recvbuf->start + bytesread;

        switch (SLPDProcessMessage(&sock->peeraddr,
                                   sock->recvbuf,
                                   &(sock->sendbuf)))
        {
        case SLP_ERROR_PARSE_ERROR:
        case SLP_ERROR_VER_NOT_SUPPORTED:
        case SLP_ERROR_MESSAGE_NOT_SUPPORTED:
            sock->state = SOCKET_CLOSE;         <======= Line 99 should not
            break;                                       exist!  
        default:


Anyway, thanks for reporting your problems.  I will make an openslp-1.0.8a 
available immediately.

-- 
Matt Peterson
Sr. Software Engineer
Caldera, Inc
ma...@ca...