[Xpipe-users] Workflows and XPipes

[Tony R. <ton...@pr...>]

I'm interested in the concept of an XPipe as a workflow engine. Obviously
any assembly line is a workflow (I'm sure Henry Ford would agree) but some
of the bigger workflow engines out there have things like event driven
processes within the flow (e.g. the car is only painted once the body is
welded together) and parallel workflow (e.g. while the car is being welded
together, the seats are being made).
	Do such complexities break the simplicity of the xpipe model or is it
possible to write some XComponents that essentially allow event and parallel
workflows? One of the things I was thinking about is that in say a parallel
workflow, each assembly line is a pipe and multiple pipes connected together
via some kind of logic would suggest a parallel workflow of sorts. If we
take that concept one step higher, then we're going to have a situation
where many different pipes can be connected to many different pipes. Thus an
xpipe has the potential to be a workflow engine. A workflow engine where
each process is simple and possible to re-use.. Lots of big vendors in that
space though....

T.