beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rich Feit <richf...@gmail.com>
Subject Re: Thread Policy on Controls...
Date Wed, 18 Jan 2006 05:36:32 GMT
I think we might get far by putting a warning on any public or 
package-protected method of a shared flow that's not marked with 
'synchronized'.  What do you think?

Daryl Olander wrote:
> Sorry, I meant that action execution is serialized but that other threads
> can run in a shared flow when the action is executing.
>
> On 1/17/06, Daryl Olander <dolander@gmail.com> wrote:
>   
>> Looks like the default for the thread policy on a control is single
>> threaded.  As described in previous mails, Shared Flows and Global App are
>> not single threaded.  I believe that action execution is single threaded,
>> but that mulitple threads can access state and call member method on a
>> shared flow while an action is running.  The question I have when the
>> control JavaDoc specifies that the infrastructure must insure only a single
>> thread will execute in a particular instance of that control at a time, does
>> this mean the control container?  If this is true, it seems to me we are
>> going to have to throw exceptions when controls that are single threaded are
>> created in either a Global App or Shared Flow.
>>
>> Does this match others understanding?
>>
>>     
>
>   

Mime
View raw message