Philipp von Weitershausen wrote:
Sure it is, I'm talking about what basically happens with nested site
managers. The problem is that the current nesting implementation seems
predicated on zodb-like persistence. I'm looking at storing all
"data", including site managers, in a relational database
On 5 Feb 2008, at 19:23 , Chris Withers wrote:
Stephan Richter wrote:
On Tuesday 15 January 2008, Chris Withers wrote:
For what I'm after, I need to have a more dynamic buildup of
registrations based on which objects have been traversed through.
Right. I think the component architecture is not
Stephan Richter wrote:
On Tuesday 15 January 2008, Chris Withers wrote:
For what I'm after, I need to have a more dynamic buildup of
registrations based on which objects have been traversed through.
Right. I think the component architecture is not really made for this.
Sure it is, I'm talkin
On Tuesday 15 January 2008, Chris Withers wrote:
> For what I'm after, I need to have a more dynamic buildup of
> registrations based on which objects have been traversed through.
Right. I think the component architecture is not really made for this. I think
it would be easier to turn on/off regi
