Re: Requirements for multiple Oak clients on the same backend (was: [suggestion] introduce oak compatibility levels)

Hi Michael, On Thu, Jul 28, 2016 at 11:03 AM, Michael Marth wrote: > ...to my knowledge there is no formal way to find out which values of X and Y > are safe - at least so far Ok, thanks for the info! That might be something to keep in mind when designing new features -

Re: Requirements for multiple Oak clients on the same backend (was: [suggestion] introduce oak compatibility levels)

Hi Bertrand, I believe this is unchartered territory. It is (usually?) safe to assume that the persistence state written by Oak version X can be read and modified by version Y if Y > X. However: version Y might introduce new features or perform changes on the state’s format, etc. When such a

Re: Requirements for multiple Oak clients on the same backend (was: [suggestion] introduce oak compatibility levels)

Don't have an answer, but there was a similar question recently on this list: "Does Oak core check the repository version ?" http://markmail.org/thread/sbvjydwdu3g2eze5 Cheers, Stefan On 28/07/16 10:45, "Bertrand Delacretaz" wrote: >Hi, > >On Thu, Jul 28, 2016 at 10:23

Requirements for multiple Oak clients on the same backend (was: [suggestion] introduce oak compatibility levels)

Hi, On Thu, Jul 28, 2016 at 10:23 AM, Stefan Egli wrote: >...we could introduce a concept of > 'compatibility levels' which are a set of features/behaviours that a > particular oak version has and that application code relies upon Good timing, I have a related