Let's see, there exists session persistent objects that we need to protect,
ie preventing a user from performing an action that will change the contents
of that object while another of his own method calls is using that object.
But these objects are only session specific, another user has his own
session object.
ex turbineresources line:
tool.session.obj = src.dataobjs.sessionobj
Therefore from what I understand, each user should be able to run there own
methods at the same time as they do not reference any of the same objects.
Unfortunately this is not happening. I was curious as to if anyone knew why
this was. The only thing I can think of, is that somehow there is something
in the RunData object, or the Velocity Context that is the same between both
sessions. This would prevent the methods from being able to run at the same
time.
From: Thomas Vandahl <[EMAIL PROTECTED]>
Reply-To: "Turbine Users List" <[email protected]>
To: Turbine Users List <[email protected]>
Subject: Re: Synchronized Velocity Actions
Date: Mon, 27 Nov 2006 20:43:17 +0100
Sheldon Ross wrote:
> Hello,
> I am currently working on the development of a large Turbine based
> project that involves a large number of database queries. The problem I
> am experiencing relates to the synchronizing of doPerform methods under
> VelocityAction.
Actually, I'm afraid I don't understand the issue. What happens in your
action that a synchronization is needed? In general, it is not a good
idea to synchronize things, especially when running a web application.
So would you please give me some insight?
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_________________________________________________________________
Get FREE company branded e-mail accounts and business Web site from
Microsoft Office Live
http://clk.atdmt.com/MRT/go/mcrssaub0050001411mrt/direct/01/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
