|
Home > Archive > WebSphere Portal Server > December 2004 > Application level data caching
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Application level data caching
|
|
| dctomlinson 2004-10-12, 9:05 am |
| Has any one come up with a mechanism for doing the following in Portal?
We have some static account structure data that we want to be able to cache and make available to all the relevant portlets.
It is a tree structure of account hierarchies, that is used throughout our 70+ portlets to define the structure of viewed data for all users. As such, it only needs to be built once and shared among all users of the application.
ANy ideas on how to approach this one? | |
| Lee Francis Wilhelmsen 2004-10-17, 5:50 pm |
| dctomlinson wrote:
> Has any one come up with a mechanism for doing the following in Portal?
>
>
>
> We have some static account structure data that we want to be able to
> cache and make available to all the relevant portlets.
>
> It is a tree structure of account hierarchies, that is used throughout
> our 70+ portlets to define the structure of viewed data for all users.
> As such, it only needs to be built once and shared among all users of
> the application.
>
> ANy ideas on how to approach this one?
Ok, I'm in a similar situation as you and need some kind of caching.
I'm thinking of looking into the WebSphere CommandCache. I've found
stuff that might get you started:
http://www-106.ibm.com/developerwor...uinnes_reg.html
http://www-106.ibm.com/developerwor...408_bernal.html
http://www-106.ibm.com/developerwor.../0410_song.html
Regards
Lee Francis
| |
| Wayne B 2004-12-11, 6:50 pm |
| dctomlinson wrote:
>
> Has any one come up with a mechanism for doing the following in Portal?
>
> We have some static account structure data that we want to be able to
> cache and make available to all the relevant portlets.
>
> It is a tree structure of account hierarchies, that is used throughout
> our 70+ portlets to define the structure of viewed data for all users.
> As such, it only needs to be built once and shared among all users of
> the application.
>
> ANy ideas on how to approach this one?
>
Why not just store it in a singleton?
Wayne
|
|
|
|
|