Thorsten Scherler wrote:
[...]
Anyway, I am as well happy to store the extension in the meta data. The
only problem is something like:
/hello/world.png
/hello/world.pdf
/hello/world.wav
...
Would you then store all this extension in the meta?
This is currently not allowed. You can't have multiple documents
with the same document ID.
means that I would need to call them:
/hello/world-png
/hello/world-pdf
...
That is the reason why I think 1) is better then 2). Here we have unique
ids.
If you use the whole request to determine the document ID, you have
to add another suffix for different presentation options:
/hello/world.xml.html
/hello/world.xml.pdf
Further how would you request e.g. /hello/world.pdf?
/hello/world.pdf
internal or http//
http://
At the moment, the suffix is not relevant for determining the document.
Do you want to pass the extension as param?
The extension is only used for presentation.
Both URLs
/hello/world.pdf
/hello/world.html
would point to the same document.
The URL suffix is used to render it as PDF or HTML, respectively.
Well not 100% true, you could store pdf and html that are not coming
from lenya and should not edit with lenya. Like pdf and html assets that
are not based on a xml. Look at the odt module.
ATM this is not supported. An exception would be thrown if you try
to add multiple documents with the same ID.
Or do you want to keep the meta like:
/hello/world.wav.meta
No, because we don't know about the ".wav" when we access the meta data :)
hmm I still not have it clear, sorry.
The meta data source URI is based on the document source URI which
contains the extension (.wav):
/foo/bar/index_en.wav
/foo/bar/index_en.wav.meta
You couldn't build the .meta URI without knowing the ".wav", which
can only be determined by reading the meta data :)
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
