🚀 go-pugleaf

In article <1b1to1INN9nj@darkstar.UCSC.EDU>, haynes@cats.ucsc.edu (Jim Haynes) writes:
|> 
|> In article <138@eiffel.eiffel.com> ram@eiffel.com (Raphael Manfredi) writes:
|> >Is there a "standard" for licence managers, something describing a formal
|> >specification of the protocol, the way keys are represented, how the client
|> >communicates with the licence manager daemon, etc...? I don't think there is,
|> >given the variety of licence managers offered by companies.
|> 
|> And I'm cynical enough to believe there isn't likely to be any standard, at
|> least for a while.  The market at present seems to consist of a several
|> license manager developers, each pushing his own proprietary product;
|> they don't want standards because their only competitive advantage is
|> in being different from all the rest.  Seems to me this isn't likely to
|> change unless some Really Big Player (e.g. Microsoft or IBM) adopts
|> a license manager protocol and makes it more affordable for software
|> developers (and end users) than any of the competing alternatives.

Well, if you believe that OSF is a standards company, then through the
Distributed Management Environment (DME), a standard license management
system will soon be available.  This is the same license management
system that has been selected by Unix International (UI) and an ever
growing number of large OEM's like: IBM, Silicon Graphics, Intergraph, 
and Hewlett-Packard.  Other large companies will soon be announcing plans 
to use this same license management system.  This technology is available
now.

The license management system used by all of the above is NetLS, the product
developed and marketed by HP/Gradient Technologies.  A number of years back
a group called the Network Computing Forum (NCF) came up with a specification
of what a "standard" license management system should look like.  The NCF
license manager spec is what the 1.1 version of the NetLS product was based
on.  The NetLS 2.0 product contains many improvements on this specification,
but still maintains an NCF compatability library for anyone who is interested
in maintaining a standard. 

Regards,

Mary
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Mary Bennett                                250 Apollo Drive
    OSSD/Distributed Object Computing Program   Chelmsford, MA  01824
    Mail Stop chd-02-co                         Telnet: 436-4266
    mob@apollo.hp.com                           mary_bennett@hpj600.hp.com
    (508) 436-4266                              FAX: (508) 256-3941
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~