Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Future of experimental leshan-server-cluster module
See original GitHub issueWe hope we will be able to release a 1.0.0 version of Leshan during this summer.
The state of leshan-server-cluster is clearly not in an acceptable state for a 1.0.0 release… So it will not be part of the release !
It seems to us that the better option is to create a new leshan-server-redis project which could include Redis store implementation. This part should be deliver in the 1.0.0 release.
All the very experimental part about northbound API would be moved in another project/repository.
(reading more about using Leshan in a cluster)
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@eliasweingaertner to be more precise, the idea is to create a
leshan-server-redismodule which will be delivered in the 1.0.0 release and which will probably contain :RedisRegistrationStorewhich storesRegistrationandObservationRedisSecurityStorewhich storesSecurityInfosRedisLockwhich is needed by both stores.(the rest go in another repositoty)
RegistrationStoreandSecurityStoreimplementation stay inleshan-server-core.#741 is now integrated in
master. Meaning that leshan-server-cluster is no more available inmaster. (leshan-server-redis is still there)The last version of leshan-server-cluster is available in branch
cluster.