Lee Carroll wrote:
In terms of the workflow history records are their any performance
implictions for large and growing xml files?
There will proably be minimal performance issues with very large files,
but that would only occur if you trigger the workflow automatically
(I guess no human being will edit and publish a document a couple of
thousand times). That issue would only affect the overall performance
if you
- have lots of documents with thousands of states in the history
- invoke actions which involve workflow operations on a lot of
these documents
The live performance of the site should not be affected at all.
If they are performance issues can I get way with removing the all but
the latest workflow state?
Yes, that should be no problem since the state machine does not
consider the history.
Ideally this would take place at a configurable point in the worklow
life cycle. (a house keep job after publication?)
Actually I see no need to have this feature in the Lenya core.
If you need it in your publication, you could probably implement
a workflow action and add it to certain transitions of the workflow schema:
http://lenya.apache.org/apidocs/1.2/org/apache/lenya/workflow/Action.html
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
