[ http://issues.apache.org/jira/browse/TAPESTRY-169?page=all ]
     
Jesse Kuhnert resolved TAPESTRY-169:
------------------------------------

    Resolution: Won't Fix
     Assign To:     (was: Tapestry Developer List)

> Synchronization problem exists for the engine within a session
> --------------------------------------------------------------
>
>          Key: TAPESTRY-169
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-169
>      Project: Tapestry
>         Type: Bug
>   Components: Framework
>     Versions: 3.0
>  Environment: Operating System: All
> Platform: All
>     Reporter: alvin shen

>
> Take an example:
> I request a page which contains a image asset. The following steps can occur 
> during processing request of this page:
> 1). The framework creates a engine instance to service this request
> 2). The application stores some data into the visit object of this engine
> 3). The framework creates a session due to visit object access
> 4). The framework renders and flushes the resulting html page
> 5). The framework stores the engine into the session previously created
> 6). The framework finishes this cycle of processing
> Between step 4 and step 5 the web browser receives and parse the html page, 
> and it continues to load the contained image, and the following steps will 
> occur at server side:
> a). Tapestry calls getEngine() which may resulting creating a new engine 
> instance, because the engine accessed in the last cycle have not yet been 
> saved to this session yet. 
> b). With this engine, tapestry continues to process the image request with 
> AssetService
> c). At this point, step 5 of last cycle occurs and the engine accessed by 
> that 
> cycle is saved to this session
> d). Tapestry continues to save engine accessed this cycle to the same session 
> which results in overrides the engine stored last cycle. And all visit data 
> associated with the overrided engine get lost!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to