Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [leshan-dev] Persistence & Clustering of Client

Vinay,

 

please also be aware of the state potentially managed at the Calfornium level, in particular if you use DTLS. Californium (or to be more precise its Scandium component) keep track of DTLS session state for each client in memory as well. Thus, if your server contains the full stack (leshan, Californium, Scandium) you will also need to take care of persisting session state at the DTLS level and probably also make your clients try to “resume” their DTLS session if they are not able to connect to the server after the server has restarted …

 

Regards,

Kai

 

From: leshan-dev-bounces@xxxxxxxxxxx [mailto:leshan-dev-bounces@xxxxxxxxxxx] On Behalf Of Simon Bernard
Sent: Thursday, January 14, 2016 6:44 PM
To: leshan developer discussions
Subject: Re: [leshan-dev] Persistence & Clustering of Client

 

You should implement your own org.eclipse.leshan.server.client.ClientRegistry, then pass it at creation :
LeshanServer server = new LeshanBuilder().setClientRegistry(new YourClientRegistry()). .... .... .build()

Le 14/01/2016 18:29, Gajjala Vinay a écrit :

Hi

 

Whenever my server is restarted it is losing the client state like registration etc., there by any update registrations after server restart from the clients are failing.

I like to know is there a way I can implement/extend the current Client cache which Leshan stores in memory to persist and share across cluster?

 

Thanks

Vinay

 

This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus. 


_______________________________________________
leshan-dev mailing list
leshan-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/leshan-dev

 

Back to the top