click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Schellink (JIRA)" <>
Subject [jira] Commented: (CLK-642) Fix the logic to manage Context with ThreadLocal
Date Sat, 13 Mar 2010 02:33:27 GMT


Bob Schellink commented on CLK-642:

Hi Henry,

Forwards are processed immediately by the container and execution returns to the original
Page after the forward is done. Thus the previous Context object is needed to continue processing
of the first page eg: onDestroy event handling.

Here is the JIRA which lead to the stack approach:

kind regards


> Fix the logic to manage Context with ThreadLocal
> ------------------------------------------------
>                 Key: CLK-642
>                 URL:
>             Project: Click
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.2.0
>            Reporter: Henry Saputra
>            Priority: Minor
>         Attachments: context_change.patch
> Currently, the Context class maintains a ThreadLocal<ContextStack> instance to
store all contexts created for each Click request. However since Clck is using  servlet mechanism,
each request will be processed in a separate thread so there should be just a single Context
in a thread execution lifetime.
> Within a thread scope, we could just use ThreadLocal<Context> to manage a single
context  since ThreadLocal guarantee a unique instance per thread.
> I dont think we need to manage the Context instances in ContextStack because there should
be only one Context instance per request, which supported by execution in a separate thread
for each request and ThreadLocal.
> I created repository for Click in to help with code review and
created an entry for this JIRA:

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message