You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Andreas Hartmann <an...@apache.org> on 2005/05/27 15:04:05 UTC
Storing workflow information in meta data
Hi Lenya devs,
now that we have mandatory meta data, it would be possible
to store the current workflow state and variable values in
there. That would rid us of the additional workflow history
file.
Actually I have a patch in my sandbox which stores the complete
history in the meta data, but that wouldn't scale and parsing
the meta data would become slower over time (at least unless
we use Jackrabbit etc.).
I'd like to propose the following approach:
- the current state and variable values are stored in the
meta data
- there is a global workflow log which can be queried to
resolve history information
This solves the performance issue and allows to get the history
information (which would be a significantly slower, but IMO this
is a rather rare usecase).
WDYT?
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Storing workflow information in meta data
Posted by "J. Wolfgang Kaltz" <ka...@interactivesystems.info>.
Andreas Hartmann schrieb:
> Hi Lenya devs,
>
> now that we have mandatory meta data, it would be possible
> to store the current workflow state and variable values in
> there. That would rid us of the additional workflow history
> file.
>
> Actually I have a patch in my sandbox which stores the complete
> history in the meta data, but that wouldn't scale and parsing
> the meta data would become slower over time (at least unless
> we use Jackrabbit etc.).
>
> I'd like to propose the following approach:
>
> - the current state and variable values are stored in the
> meta data
>
> - there is a global workflow log which can be queried to
> resolve history information
>
> This solves the performance issue and allows to get the history
> information (which would be a significantly slower, but IMO this
> is a rather rare usecase).
>
> WDYT?
+1
IMO this is a good separation of concerns (current state / history of
states are 2 different concerns).
--
Wolfgang
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Storing workflow information in meta data
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Andreas Hartmann wrote:
> now that we have mandatory meta data, it would be possible
> to store the current workflow state and variable values in
> there. That would rid us of the additional workflow history
> file.
>
> Actually I have a patch in my sandbox which stores the complete
> history in the meta data, but that wouldn't scale and parsing
> the meta data would become slower over time (at least unless
> we use Jackrabbit etc.).
>
> I'd like to propose the following approach:
>
> - the current state and variable values are stored in the
> meta data
>
> - there is a global workflow log which can be queried to
> resolve history information
>
> This solves the performance issue and allows to get the history
> information (which would be a significantly slower, but IMO this
> is a rather rare usecase).
+1 it is a good idea to unifiy this mandatory metadata. makes it easier
to map it to jcr:attributes later
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org