Re: Best practice to run threads from processElement

Hi Matze,

Participants give you an application-wide thread that you can easily  
access from a single repository. For there rest, there are other  
advantages, like exposing results and waiting for objects from other  
participants to create a kind of automating dependency management, but  
I don't think this would benefit you.

I don't think I'd use participants for your use case.

HTH,

Geert

On 29 May 2009, at 16:48, Matthias Barmeier wrote:

>
> Hi Geert,
>
> I need a dispatcher thread that collects packaging orders and than
> starts for everey order a packing thread.
> The Queue/Processing skeleton is already implemented. Though, I  
> think I
> will give a try for the participant or do you think that this
> have some disadvantages that your approach does not have ?

--
Geert Bevin
Terracotta - http://www.terracotta.org
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Flytecase Band - http://flytecase.be
Music and words - http://gbevin.com


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-users" group.
To post to this group, send email to rife-users@...
To unsubscribe from this group, send email to rife-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-users?hl=en
-~----------~----~----~----~------~----~------~--~---