First off, you should look at the data caching feature in ND5 to see if
that might do something for you.
^^^^^^^
whoops,
that's available as of ND4 -- Curt
Anyhow, I've got some stuff that caches rows, on a session basis.
Question: are you trying to cache data for use in one session or across
multiple sessions?
If for one session, I would put the data into a session object. In each
page get the session object in onBeforeLoad or button/href web events, put
it back at the end of processing. I keep rows from up to 30 tables in
memory on this basis.
At one point, I had a singleton class, and it killed performance. I found
that it worked to have one object of the class owned by each page class,
since much of ND's object instantiation model is driven at the page level.
You should also look at EJB in ND5. That would be a cleaner implementation
than anything available in ND4, except maybe a PAC.
-- Curt Springer, Team ND
At 04:08 PM 4/15/99 -0800, [EMAIL PROTECTED] wrote:
>In our architecture, we have a Cache Manager component which caches the
data (in memory) to
>reduce trips to the DB. Cache Manager is a singleton, i.e. there is only
one instance of Cache Manager.
>What is the best way to implement the Cache Manager in ND so that the
cached data
>is accessible to other services?
>
>Thanks...
>
>Raj
>
>_________________________________________________________________________
>
>For help in using, subscribing, and unsubscribing to the discussion
>forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
>
>For dire need help, email: [EMAIL PROTECTED]
>
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
