[How-to] Object versioning at server side
See original GitHub issueHello guys, Do you have any advices on how to best implement object versioning on the server side. The idea is that we will have different devices connecting to our server. Each one with different object versions of course. However, on each connection we need to do a number of actions on the device (read battery levels, location, etc…). So I need to support multiple object versions at the same time. I am not sure how to do it on the code side. Do you have any advice you could give?
Thanks
PS: I am using the VersionedModelProvider
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Use Object Versioning | Cloud Storage
In the Object versioning section, click the current status to make changes to it. The Object versioning dialog box appears. If you're enabling...
Read more >Using versioning in S3 buckets - AWS Documentation
You can use the S3 Versioning feature to preserve, retrieve, and restore every version of every object stored in your buckets. With versioning...
Read more >Support of object versioning at server side. · Issue #535 - GitHub
The support of object version was added by #438, but to be really useful at server side we need a kind of ObjectModelRepository...
Read more >MinIO Versioning, Metadata and Storage Deep Dive
Dig into MinIO internals and learn how this distributed object storage ... had versioning enabled since the customer was using serverside ...
Read more >Versioning objects - IBM Cloud Docs
Getting started with versioning · After navigating to your object storage instance, click on Create bucket. · Choose a region and resiliency, then...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
So let’s say you have :
So device A will register itself with
...</3/0>,</26243/0> ...
And device B with...</3/0>,</26243>;ver=2.0</26243/0>, </26244/0>...
(v1.0 is not visible because this is the default value)With this information Leshan will be able to automatically decode or encode value correctly. But it can not decide at your place that you should read 26244/0/1 instead of 26243/0/1 … (or read on 26244/0 instead of 26243/0) So it’s up to you to send the right request. To know which request you need to send you can use
Registration.getSupportedVersion(26243) == "1.0"
orRegistration.getSupportedVersion(26244) != null
Thanks for the help closing this 😄