blucove stack shutdown programmatically

[magnas]

Hello,

is there anyway to shutdown the bluecove stack programmatically?

I'm using the stack of WIN XP

Thanks

[magnas]

Hello,

I need to shutdown the bluecove stack programmatically.

I've downloaded ver2.0.3 and used the shutdown method but I don't
think it works

[Armando Périco]

I'm using 2.0.3 too under Linux and Mac OS, and is not working
neither, also RemoteDeviceHelper.authenticate("","pass") is not
working here....

any idea ?

Thanks a lot!

[Vlad Skarzhevskyy]

RemoteDeviceHelper.authenticate(..., pin) is only for WIDCOMM stack.
Contributions welcome for other stacks. Authentication at all is not
implemented at all on Linux . the same contributions welcome .

Also why do you think that shutdown() is not working? It is closing
API handlers so it can be open again. It does not promise to close all
open connections. Did you expected that?

The only place it does really close connections is bluecove-emu where
this is required for unit tests to continue.

--
Vlad

[magnas]

Hello,
Yes I was expecting it to close all open connections....also after I
used shutdown() how can I check that the stack actually down?
Should I expect any messages returned like when the stack is shutdown
normally?

Thanks

On May 3, 11:39 pm, "Vlad Skarzhevskyy" <skarzhevs...@gmail.com>
wrote:

> RemoteDeviceHelper.authenticate(..., pin) is only for WIDCOMM stack.
> Contributions welcome for other stacks. Authentication at all is not
> implemented at all on Linux . the same contributions welcome .
>
> Also why do you think that shutdown() is not working? It is closing
> API handlers so it can be open again. It does not promise to close all
> open connections. Did you expected that?
>
> The only place it does really close connections is bluecove-emu where
> this is required for unit tests to continue.
>

[Vlad Skarzhevskyy]

Honestly I would expect it to close connections as well.
So I just added the functions to close incoming and outgoing connections.
TODO is to closed services. Since I don't keep list of them in
implementation this will take some work.

Also there is no way to say that shutdown() is completed because any
new call to open connection will initialize the stack again.