Re: [ecf-dev] SLP Question

[Jim Marshall <jm109344@xxxxxxxxx>]

Yes I am referring to the jSLP feature of starting its own
implementation when it doesn't detect an external one running on port
427.

A specific example would be someone embedding our product as a Servlet
and then having that Servlet redeployed. Since the SLP threads don't
exit the Servlet doesn't fully shut down and they need to restart the
entire server (Apache in this case).

I think I can make the changes I need for it to function how we want,
I just wanted to make sure I wasn't missing something.

Thanks for the reply.
Jim

On Thu, Aug 21, 2014 at 5:37 AM, Markus Alexander Kuppe
<ecf-dev_eclipse.org@xxxxxxxxxxx> wrote:
> On 20.08.2014 20:33, Jim Marshall wrote:
>>  Hope this is the right group for this question. We're using the SLP
>> portion of the ECF tree in our product.
>>
>> The SLP code starts its own daemon server if there is no other slp
>> daemon running (which is what we want), however; we do not see a way
>> to tell the daemon to stop or exit.  Would anyone know if there is
>> some mechanism to do this?
>
> Hi Jim,
>
> yes, this is one place to ask jSLP v1 related questions.
>
> However, can you clarify if - by SLP daemon - you are talking about
> jSLP's feature to uses an existing external SLP daemon running on the
> same host and falling back to its own implementation [1] when no
> external daemon can be detected (on port 427)?
> If this is the case, then I'm afraid jSLP does not support stopping its
> own daemon once it has created an internal one. You will have to restart
> the jSLP process.
>
> What is your underlying use case, anyway?
>
> M.
>
> [1] ch.ethz.iks.slp.impl.SLPDaemonImpl
> _______________________________________________
> ecf-dev mailing list
> ecf-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/ecf-dev