Am 17.12.2007 um 15:40 schrieb Jim Fulton:
On Dec 17, 2007, at 8:22 AM, Christian Zagrodnick wrote:
Hi,
a couple of weeks ago there was some discussion about the skin/ layer support for XML-RPC which I implemented without asking (shame on me). As some time has passed now everybody could have some fresh thoughts about it.
Let me first summarise:
* Skin and layers should be seen as typing the request.
* There are no general objections against having layers for XML-RPC.
I have a general objection for reasons of complexity. Why do we need this?
About the specifics with skins for other protocols than http I can not say much.
In fact, I find skins in general to introduce more complexity than they're worth.
This baffles me somewhat. At the moment I see skins/layers as the only mechanism to let developers using an application to customize it, possibly more than once in the same instance. I find them not optimal, because they only allow customizing on the outer most level. But overrides is a failure as I understand it. I understand, that there is a trend to distinguish between "libraries" (with less zcml) and "applications" (with zcml to configure reused libraries). But on the level of applications I know of no other mechanism than layers. So what should be used or invented instead? As a usecase take a forum application which should be installed more than once in an instance but needs different layouts and also different subset of functionality. With regards, __Janko -- Janko Hauser email: jhauser@zscout.de mobile: +49 1721 641552