Wasn't sure what to call this.
I have a need to make some shared information available to components. I'd
want the information cached in memory to cut down on the overhead of reading
it from the filesystem or database. I'll need it within custom generators
for now, but it'd be a plus to
On Thursday 06 June 2002 11:45 am, Geoff Howard wrote:
I thought of defining a singleton class with public
getSubsiteID(page-layoutID) methods, etc. but thought there was a more
cocoon way of doing this that would make the availibilty more general.
There is, create a new component!
Define a
-Original Message-
From: Peter Royal [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 06, 2002 11:51 AM
To: [EMAIL PROTECTED]
Subject: Re: Best Practice for shared information lookup? Modules?
On Thursday 06 June 2002 11:45 am, Geoff Howard wrote:
I thought of defining a singleton class
On Thursday 06 June 2002 01:01 pm, Geoff Howard wrote:
I can certainly play with this solution - Do I need to define the role
anywhere else? I had thought there was a ?.roles file somewhere.
The role attribute on the component-instance tag will suffice. The other
choice is to create your own
Geoff Howard wrote:
Wasn't sure what to call this.
I have a need to make some shared information available to components. I'd
want the information cached in memory to cut down on the overhead of reading
it from the filesystem or database. I'll need it within custom generators
for now, but
Geoff Howard wrote:
Wasn't sure what to call this.
I have a need to make some shared information available to components. I'd
It depends where you need this information and what kind of information
it is.
If it is simple (small), needed by the sitemap, existing sitemap
components or
]
Subject: Re: Best Practice for shared information lookup? Modules?
Geoff Howard wrote:
Wasn't sure what to call this.
I have a need to make some shared information available to
components. I'd
It depends where you need this information and what kind of
information
