[ http://issues.apache.org/jira/browse/COCOON-1683?page=all ]
Johan Stuyts closed COCOON-1683:
Resolution: Fixed
Allow configuration of expiry in EHDefaultStore
---
Key: COCOON-1683
Reporter: Johan Stuyts
Attachments: cocoon-ehdefaultstore-configurable-expiry.patch
EHDefaultStore initializes the cache to never expire entries. This means that
the cache will grow indefinitely (on disk).
This patch allows you to set the expiry of entries in the configuration so that
stale entries
null;
}
'allowBackwardCompatibleContinuationSharing' will be a configuration option
which defaults to 'false'.
If nobody objects I will make the changes, create patches and add a new bug for
this.
Johan Stuyts
Hippo
-Original Message-
From: Carsten Ziegeler [mailto:[EMAIL PROTECTED
On Thu, 18 Mar 2004 00:19:09 +0100, Michael Wechner
[EMAIL PROTECTED] wrote:
Johan Stuyts wrote:
I view choosing for Lenya workflow as choosing to build/use a
Cocoon-independent solution (with an adapter to make it accessible in
Cocoon) instead of building a solution using Cocoon-specific
are license-compatible with Cocoon.
+1 to start with Lenya workflow.
Guido
(How long until Andreas returns from vacation? :-)
Michi
--
Johan Stuyts
usability.
It might be an option to choose a (proper) subset of a standard with which
a large percentage (definitely more than 80%. Having to resort to another
solution in one of four situations is not acceptable) of use cases can be
implemented.
--
Johan Stuyts, Software Department
Hippo Webworks
definition can have a mapping from old
state identifiers to new state identifiers.
Other information needed for proper processing should be stored with the
object.
--
Johan Stuyts
A summary of my interpretation of the workflow thread is available on the
wiki (http://wiki.cocoondev.org/Wiki.jsp?page=Workflow). Please verify my
findings and I'm sorry if I misinterpreted something.
--
Johan Stuyts
On Mon, 08 Mar 2004 19:58:32 +0100, Guido Casper [EMAIL PROTECTED]
wrote:
Johan Stuyts wrote:
Using the GoF State pattern works great for simple state machines and I
use it a lot. But the pattern does not talk about nested and/or
parallel states, which become incomprehensible when coded
for that, instead of spending too much time on the
whiteboard without getting anything out of the door.
--
Johan Stuyts
fine.
--
Johan Stuyts
shouldn't give a damn about other
states: transactions might need that.
Yes, maybe they are misnamed. Just replace states with transaction
(or even better transitions).
Yepp, transitions of course, sorry for the misnaming. :-)
Ciao,
--
Johan Stuyts
On Mon, 08 Mar 2004 11:41:12 +0100, Unico Hommes [EMAIL PROTECTED] wrote:
Johan Stuyts wrote:
On Fri, 05 Mar 2004 17:18:53 -0500, Stefano Mazzocchi
[EMAIL PROTECTED] wrote:
Johan Stuyts wrote:
Experience with workflow at Hippo Webworks
==
At Hippo we
://wiki.cocoondev.org/Wiki.jsp?page=Workflow) with our experiences.
Johan Stuyts
Hippo Webworks
http://www.hippo.nl/
johan (at) hippo (dot) nlattachment: StateMachine.png
14 matches
Mail list logo
