On Fri, May 19, 2000 at 09:00:35PM -0500, dave bryson wrote:
Go for it.
Good catch! How the hell did we miss that for so long!?
Well it's only the fact that ScreenLoader caches screens that makes this
a problem, and that's pretty hidden from view unless you go looking.
--
Sean Legassick
on 5/20/2000 7:24 AM, Sean Legassick [EMAIL PROTECTED] wrote:
Well it's only the fact that ScreenLoader caches screens that makes this
a problem, and that's pretty hidden from view unless you go looking.
and that caching is turned off by default...
i get it now, we are doing a new instance
On Fri, 19 May 2000, you wrote:
on 5/19/2000 7:00 PM, dave bryson [EMAIL PROTECTED] wrote:
Go for it.
Good catch! How the hell did we miss that for so long!?
Ok...the fixes are in CVS...I decided to add the context to the
doBuildTemplate() method so that it is passed in...that way
Hey all,
I just realized that the context object could potentially be overwritten by
another thread. We can't have it defined as a variable in the instance of
WebMacroSiteScreen because that needs to be MT...
am i wrong here?
-jon
--
Java Servlet Based - Open Source |Collab.Net
Subject: Context syncronization problem?
Hey all,
I just realized that the context object could potentially be overwritten
by
another thread. We can't have it defined as a variable in the instance of
WebMacroSiteScreen because that needs to be MT...
am i wrong here?
-jon
--
Java
On Fri, 19 May 2000, you wrote:
so, this is going to have to be the solution. ug. dave, do you want to do
the fix or me? i'm willing to do it...
Go for it.
Good catch! How the hell did we miss that for so long!?
--
dave
[EMAIL PROTECTED]
--
your inspirational quote
on 5/19/2000 7:00 PM, dave bryson [EMAIL PROTECTED] wrote:
Go for it.
Good catch! How the hell did we miss that for so long!?
Ok...the fixes are in CVS...I decided to add the context to the
doBuildTemplate() method so that it is passed in...that way we still get
around the issue of me not
