Re: [1.4] UUIDs and content storage

2006-08-09 Thread solprovider
On 8/9/06, Joern Nettingsmeier <[EMAIL PROTECTED]> wrote: Andreas Hartmann wrote: > Hi Lenya devs, > documents are now stored in the following structure: > content/// > .meta > Example: > content/authoring/550e8400-e29b-11d4-a716-44665544/de >

Re: [1.4] UUIDs and content storage

2006-08-09 Thread Andreas Hartmann
Joern Nettingsmeier wrote: [...] side question: is the area concept now fixed "forever", or will it be possible to re-discuss it after 1.4 is out without affecting too much of your current storage layer work? The API will be fixed. If we provide a migration tool we can certainly change the st

Re: [1.4] UUIDs and content storage

2006-08-09 Thread Joern Nettingsmeier
Andreas Hartmann wrote: > Hi Lenya devs, > > documents are now stored in the following structure: > > content/// > .meta > > Example: > > content/authoring/550e8400-e29b-11d4-a716-44665544/de > de.meta >

Re: [1.4] UUIDs and content storage

2006-08-09 Thread Michael Wechner
Andreas Hartmann wrote: Hi Lenya devs, documents are now stored in the following structure: content/// .meta Example: content/authoring/550e8400-e29b-11d4-a716-44665544/de de.meta

Re: [1.4] UUIDs and content storage

2006-08-09 Thread Doug Chestnut
Andreas Hartmann wrote: Hi Lenya devs, documents are now stored in the following structure: content/// .meta Example: content/authoring/550e8400-e29b-11d4-a716-44665544/de de.meta

[1.4] UUIDs and content storage

2006-08-09 Thread Andreas Hartmann
Hi Lenya devs, documents are now stored in the following structure: content/// .meta Example: content/authoring/550e8400-e29b-11d4-a716-44665544/de de.meta