Should there be a mechanism to persist data?

[codeundkakao]

Thinking of a car context (or any similar system) there certainly needs to be a mechanism in place to persist data to survive server restarts. Does viwi specify a certain mechanism for persistence or is there a desired and/or suggested path on which to approach that goal?

[wzr1337]

There is no such mechanism so far.. Anyway, starting out with a key Value store might be nice, such as local storage. Any object would contain an Id name and Uri plus a value. This value is a string so you can encode what ever you like. The name is the key, the Id is just a non-human-readable equivalent. A query like GET /persistence/values/?name=my key Would return a lost of all values with key mykey What do you think?

On Wed 12. Apr 2017 at 16:15 alexander thieme ***@***.***> wrote: Thinking of a car context (or any similar system) there certainly needs to be a mechanism in place to persist data to survive server restarts. Does viwi specify a certain mechanism for persistence or is there a desired and/or suggested path on which to approach that goal? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#30>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADiF7fdMVR0dlXouwMbZyKjHk-fYXJWWks5rvNx9gaJpZM4M7fGt> .

-- - Patrick (Mobile)

[codeundkakao]

Sorry for the late reply.

If I understand your suggestion correctly, this would mean 'persistence' would be implemented as a plugin or service respectively within which 'values' is a resource and whatever gets stored in there would be elements like in the current plugin structure, right?

This also means that any plugin could implement it's own persistence mechanism just like that. Would this also allow plugins to use this service internally to store data and retrieve it back at startup maybe?