On 8/25/06, Andreas Hartmann <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote: > 1.4 has two protocols for accessing content? XMAP developers must > decide which is appropriate for each match? Sometimes language is > required, but sometimes it is optional? <map:match > pattern="/mypipeline/**"> must know whether ** is an ID or a UNID? I think it should be stated explicitely how you address a document. I don't like the approach of allowing UUIDs and site structure paths in the same protocol.
Both Authoring and Live Modules call DocumentTypeModules to retrieve the XML. They pass the current URL. Authring uses UUIDs. Live uses IDs. The DocumentTypeModule contains: <map:match pattern="/doctype/**"> <map:generate src="content:/(1)"> Lenya should make everything as easy as possible. If different protocols are required based on the calling method, more pipelines are needed. More pipelines = more work = not as easy as possible. Besides, it is easy for one protocol to handle both cases. If there are no slashes after the protocol specification, try to retrieve using it is a UUID. If it does not exist, or if there were slashes, try using it as an ID.
> If defaultlanguage is not by Resource, every page will default to the > default language. Hmm, what's wrong with that? > Everybody will set the default language to "xx" so > only items in that non-existent language will use a default. Why make > people use workarounds? Sorry, I don't understand that ... Why should someone want to set the default language to "xx"?
There is a multi-language pub. Each language should only show each Resource if the Translation exists. The Publication's defaultlanguage is "en". If the request does not contain a language, "en" is used. We then retrieve the Resource. With Resource-specific default languages, if the Resource does not contain the specified translation, it can fail. Without Resource-specific default languages, if the Resource does not contain the specified translation, it returns the defaultlanguage Translation. But if the specified Translation does not exist, you do not want it to appear. You still need a defaultlanguage so images only need one Translation, so as a workaround, you create a fake language "xx" for use as the defaultlanguage. The workaround has side-effects, such as each Resource having an extra language on its language choice menu. The defaultlanguage of a pub should only be used if no language is specified. A Resource-specific defaultlanguage allows some Resources to have many Translations with failure if the requested one does not exist, and other Resources with a default Translation. Again, it was easy to add the defaultlanguage attribute at the Resource level (above the Translation level: Resource/Translation/Revision). solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
