I'm using a modified version of the workflow component of the krysalis project.
I want to store persistently states of this workflow, these states could bo modelized as beans (java objects with attributes to be precise). These objects could be numerous (a thousand ?). I'm looking for the best manner to store these objects :
- database mapping (the best solution I think) with light memory store (caching ? complete light model ?)
- excalibur store (filesystem access = overload ?)
And I'm wondering if the store defined in the cocoon.xconf is ready to use for client app or if it is already used by Cocoon components...
I hope I'm clear ;)
-- Olivier
On 13/08/2003 23:27, Geoff Howard wrote:
Olivier Billard wrote:
Hi all,
I would like to use store components for persistent storage.
Why?
Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
