Hi Eugene,
OK. I would like to discuss it in an issue.
There is some to define in the wording, e.g. server and client, and coap-server and coap-client. Because, if you restart the server, you restart the coap-client of your observes.
There is some kind of support for that, because leshan requires that as well. But it’s currently not “out of the box”.
The easier solution is, just to reestablish a new observation, when you server (coap-client) restarts.
Mit freundlichen Grüßen / Best regards
Achim Kraus
(INST/ECS4)
Bosch Software Innovations GmbH | Stuttgarter Straße 130 | 71332 Waiblingen |
GERMANY |
www.bosch-si.com
Tel. +49 711 811-58139 | Fax +49 711 811-58200 | achim.kraus@xxxxxxxxxxxx
Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B
Aufsichtsratsvorsitzender: Dr.-Ing. Thorsten Lücke; Geschäftsführung: Dr. Stefan Ferber, Michael Hahn
From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Eugene Nikolaev
Sent: Dienstag, 23. Januar 2018 16:07
To: Californium (Cf) developer discussions <cf-dev@xxxxxxxxxxx>
Subject: Re: [cf-dev] Restore an observe relation after restart
- an embedded device connects to a Californium server.
- server sets up an observe relation
- embedded device sends notification when has data
- I restart a Californium server due to redeploy and
new instance of Californium does not know about that relation since they were stored in-memory
I'd like to restore that observe relation somehow.
Or at least catch that unknown Observe notification.
BTW what is preferred for such questions: this mailing list or creating a github issue?