On 5/26/07, Joern Nettingsmeier <[EMAIL PROTECTED]> wrote:
Andreas Hartmann wrote:
> Thorsten Scherler schrieb:
>> On Fri, 2007-05-25 at 11:07 +0200, Andreas Hartmann wrote:
>>> Hi Lenya devs,
>>>
>>> this is a serious and quite urgent issue because it blocks the RC.
>>> It would be great if we could get more opinions.
>>>
>>> For more information, please see
>>> http://www.nabble.com/Status-of-proxying-issue-for-1.4-tf3794430.html
>>>
>>> IIUC Thorsten prefers the global proxy URL, Michi and I prefer the
>>> reserved URL space.
>> The problem with reserved url spaces for modules is that it is highly
>> confusing. Why should we prefix global modules with pubs/area? That does
>> not make sense for me. Publication specific modules yes, global no.
>
> In principle I agree, but this is one of the rare occasions where
> I'd prefer to handle the issue pragmatically. For my personal use
> of Lenya it is very important that the URL space of a website is
> self-contained, preferrably without extra configuration or
> implementation.
>
> Of course I could add hooks to my publication which map the module
> URL spaces into the publication URL space. And I'm quite confident
> that many people will do this, ending up with a lot of boilerplate
> code.
i agree that thorsten's suggestion is more awkward to use. i prefer it
nonetheless. it requires some extra configuration work, but it gets the
job done without implicit semantics... clogging the publication URI
space is a serious decision, and if we make it now, we make it for some
time to come. i'd like to rethink both context prefix and proxy url
handling for the next major lenya release anyway - that's why i'd prefer
a slightly awkward solution without subtle implications over a pragmatic
one that leaves us with cruft in the future...
lenya is a multi-publication cms, hence it is quite natural that it
should have global resources.
a self-contained URI space for publications is a good argument, but you
can easily achieve that in your publication sitemap - i.e. you add
boilerplate code when you need something special, which is ok (adding
boilerplate code for standard scenarios is not imho).
regards,
jörn
A Publication ...
- has a datastore for resources (file system, Jackrabbit, etc.)
- defines access control (file system, LDAP, etc.)
- includes functionality (local or inherited from global.)
- is the root of a Lenya website.
Lenya should define a default publication for requests with no
publication specified.
What functionality is independent of a publication? Adding and
deleting Publications is the only functionality I would expect to
apply at the server level. That could be implemented with an
administration publication.
What am I missing?
solprovider
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
