Skip to content.

Manageability

Sections
Personal tools
You are here: Home » blog » stuff » why? concurrent != threads?

Comment

Above in this comment thread: Open Source Workflow Engines Written in Java » Concurrent processing of splits? » concurrent processing

why? concurrent != threads?

Posted by Anonymous User at 2006-03-12 11:29 AM

I'm a workflow rookie alright so maybe I'm way off base, but when my workflow splits no user interaction is required on either subflow until after the join has been performed. Every step has an automatic start and finish too. So I dont really understand why the workflow engine could not process these in parallel ... literaly on separate threads. Why is there a pseudo sequencial process enforced?

Can you help me understand? What exactly are concurrent workflows? Is there any way of achieving this multithreaded processing? Must I do it within an activity?

Thanks in advance

1142436317

Posted by Anonymous User at 2006-03-15 09:25 AM

do you care about how it's done behind ? As long as it seems parallel...

 
 

Powered by Plone

This site conforms to the following standards: