Hi

Pretty much exactly! How do I force this behaviour?

Thanks, Noel.

Hird Matthew wrote:
> Noel,
>  
> You can force the jSLP solution to always start up as a UA/SA. ie.
> don't start as a daemon. That way, you'd never have a daemon running
> for the scope you are in and so would fall back to multicast.
>  
> Would that work for you?
>  
> cheers,
> Matt
>
>     -----Original Message-----
>     *From:* Noel Grandin [mailto:[EMAIL PROTECTED]
>     *Sent:* 21 May 2008 09:50
>     *To:* Hird Matthew
>     *Cc:* 'openslp-users@lists.sourceforge.net'
>     *Subject:* Re: [Openslp-users] java library still active?
>
>     Hi Matt
>
>     It's not so much about scalability of no_of_applications or
>     application_size but rather scalability of
>     my_available_support_time :-)
>
>     I never fully control the places where my applications are
>     installed, and customers have a bad habit of accidentally
>     uninstalling or turning off any additional system services I may
>     install, so I don't like relying on them if I can avoid it.
>
>     Which pretty much rules out a standalone SLP system daemon.
>
>     And I'm pretty much guaranteed to be sharing the system with some
>     other applications that I don't own that are also going to be
>     implementing my service-locator protocol, and I really hate
>     getting into a situation where someone else's application can
>     disrupt my application.
>
>     Which pretty much rules out running the SLP deamon process inside
>     the first application that starts up.
>
>     So I'm going to implement my own variant of SLP that uses pure
>     multicast to do the service requests, and dynamic unicast server
>     ports for the replies. Not as scalable as SLP, but it's good
>     enough for my purposes.
>
>     Regards, Noel.
>
>
>     Hird Matthew wrote:
>>     Hi Noel,
>>      
>>     How many apps are we talking about here? We've quite a bit of
>>     experience now using OpenSLP with jSLP for both C++ and Java
>>     apps. Our system is very large so we have massive scalability.
>>      
>>     I'm pretty sure there must be a way to do what you want with SLP.
>>      
>>     Matt
>>
>>         -----Original Message-----
>>         *From:* Noel Grandin [mailto:[EMAIL PROTECTED]
>>         *Sent:* 21 May 2008 08:55
>>         *To:* Hird Matthew
>>         *Cc:* 'openslp-users@lists.sourceforge.net'
>>         *Subject:* Re: [Openslp-users] java library still active?
>>
>>         Hi Matt
>>
>>         Thanks for all your help.
>>
>>         I want my application to run standalone, with as few
>>         dependencies on external services as possible.
>>         Installing extra system services is a no-no because it
>>         increases the likelihood of a customer accidentally breaking
>>         the configuration.
>>
>>         Bummer. I'm going to have to implement my own protocol to do
>>         this.
>>         I know it won't scale as well as SLP, but I'm happy to trade
>>         off some extra network traffic for increased application
>>         reliability.
>>
>>         Regards, Noel.
>>
>>
>>         Hird Matthew wrote:
>>>         Noel,
>>>
>>>         Why don't you run the OpenSLP solution as a daemon and let your 
>>> java apps
>>>         run as UAs? That's what we do.
>>>
>>>         cheers,
>>>         Matt
>>>
>>>         -----Original Message-----
>>>         From: Noel Grandin [mailto:[EMAIL PROTECTED]
>>>         Sent: 20 May 2008 11:13
>>>         To: Morrell Richard
>>>         Cc: 'openslp-users@lists.sourceforge.net'
>>>         Subject: Re: [Openslp-users] java library still active?
>>>
>>>
>>>         Hi Richard
>>>
>>>         Aah, I see from reading the spec that SLP uses both multicast and
>>>         unicast messages. Which is why only one application on a machine 
>>> can be
>>>         "the daemon".
>>>
>>>         Is there any way to force an SLP client into a mode where it only 
>>> works
>>>         with multicast i.e. where every application runs its own daemon?
>>>         This should be fine since multiple applications on the same machine 
>>> can
>>>         bind to the same multicast port.
>>>
>>>         It really is a deal-breaker for me if I end up with 
>>> inter-application
>>>         dependencies, and I'd prefer not to invent my own protocol.
>>>
>>>         Am I missing something?
>>>
>>>         Regards, Noel.
>>>
>>>         Morrell Richard wrote:
>>>           
>>>>         No, only one daemon can run on any single machine, as it has to 
>>>> bind to
>>>>             
>>>         the
>>>           
>>>>         SLP port (427).
>>>>
>>>>         The jSLP implementation tries to bind to port 427 when it starts 
>>>> up, and
>>>>             
>>>         if
>>>           
>>>>         it can't do so, just acts as a UA.  Hence, the first Java app that 
>>>> runs on
>>>>             
>>>         a
>>>           
>>>>         machine sets itself up as a daemon, and the rest run as UAs.  Note 
>>>> that,
>>>>             
>>>         on
>>>           
>>>>         Unix machines, an app must be running as root to be able to bind 
>>>> to port
>>>>         427.
>>>>           
>>>>             
>>>
>>>
>>>         Disclaimer: http://www.peralex.com/disclaimer.html
>>>
>>>
>>>
>>>         
>>> -------------------------------------------------------------------------
>>>         This SF.net email is sponsored by: Microsoft 
>>>         Defy all challenges. Microsoft(R) Visual Studio 2008. 
>>>         http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>>         _______________________________________________
>>>         Openslp-users mailing list
>>>         Openslp-users@lists.sourceforge.net
>>>         https://lists.sourceforge.net/lists/listinfo/openslp-users
>>>
>>>         This email, including any attachment, is a confidential 
>>> communication
>>>         intended solely for the use of the individual or entity to whom it 
>>> is
>>>         addressed. It contains information which is private and may be 
>>> proprietary
>>>         or covered by legal professional privilege. If you have received 
>>> this email
>>>         in error, please notify the sender upon receipt, and immediately 
>>> delete it
>>>         from your system.
>>>
>>>         Anything contained in this email that is not connected with the 
>>> businesses
>>>         of this company is neither endorsed by nor is the liability of this 
>>> company.
>>>
>>>         Whilst we have taken reasonable precautions to ensure that any 
>>> attachment to
>>>         this email has been swept for viruses, we cannot accept liability 
>>> for any
>>>         damage sustained as a result of software viruses, and would advise 
>>> that you
>>>         carry out your own virus checks before opening any attachment.
>>>
>>>
>>>           
>>
>>
>>
>>
>>         
>> ------------------------------------------------------------------------
>>         Disclaimer: http://www.peralex.com/disclaimer.html
>>
>>
>>     This email, including any attachment, is a confidential
>>     communication intended solely for the use of the individual or
>>     entity to whom it is addressed. It contains information which is
>>     private and may be proprietary or covered by legal professional
>>     privilege. If you have received this email in error, please
>>     notify the sender upon receipt, and immediately delete it from
>>     your system.
>>
>>
>>     Anything contained in this email that is not connected with the
>>     businesses of this company is neither endorsed by nor is the
>>     liability of this company.
>>
>>
>>     Whilst we have taken reasonable precautions to ensure that any
>>     attachment to this email has been swept for viruses, we cannot
>>     accept liability for any damage sustained as a result of software
>>     viruses, and would advise that you carry out your own virus
>>     checks before opening any attachment.
>>
>>
>
>
>
>
>     ------------------------------------------------------------------------
>     Disclaimer: http://www.peralex.com/disclaimer.html
>
>
> This email, including any attachment, is a confidential communication
> intended solely for the use of the individual or entity to whom it is
> addressed. It contains information which is private and may be
> proprietary or covered by legal professional privilege. If you have
> received this email in error, please notify the sender upon receipt,
> and immediately delete it from your system.
>
>
> Anything contained in this email that is not connected with the
> businesses of this company is neither endorsed by nor is the liability
> of this company.
>
>
> Whilst we have taken reasonable precautions to ensure that any
> attachment to this email has been swept for viruses, we cannot accept
> liability for any damage sustained as a result of software viruses,
> and would advise that you carry out your own virus checks before
> opening any attachment.
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft 
> Defy all challenges. Microsoft(R) Visual Studio 2008. 
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Openslp-users mailing list
> Openslp-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openslp-users
>   


Disclaimer: http://www.peralex.com/disclaimer.html


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Openslp-users mailing list
Openslp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openslp-users

Reply via email to