Yep, that's exactly how you should do it.
On 8/3/07, Ben Dotte <[EMAIL PROTECTED]> wrote:
> Yes, a threaded service is created and bound to the current request
> thread the first time it is requested. There is a more detailed
> explanation here:
>
> http://hivemind.apache.org/hivemind1/services.ht
Ok, yeah actually Tapestry's ApplicationServlet takes care of the
HiveMind filter so nevermind that part:
http://tapestry.apache.org/tapestry4.1/usersguide/hivemind.html#Bootstrapping%20the%20Registry
On 8/3/07, Ben Dotte <[EMAIL PROTECTED]> wrote:
> Yes, a threaded service is created and bound t
Yes, a threaded service is created and bound to the current request
thread the first time it is requested. There is a more detailed
explanation here:
http://hivemind.apache.org/hivemind1/services.html#Threaded+Service+Model
They also mention on there how to handle cleanup at the end of the
reques
On Thu, Aug 02, 2007 at 10:12:14AM -0500, Ben Dotte wrote:
> Is there any reason you can't use a threaded HiveMind service? That is
> usually the approach I take when I have a shared resource that should
> only live for the duration of a request.
Thanks for the tip. I'm not quite sure if this work
Hi Christian,
Is there any reason you can't use a threaded HiveMind service? That is
usually the approach I take when I have a shared resource that should
only live for the duration of a request.
Ben
On 8/2/07, Christian Haselbach <[EMAIL PROTECTED]> wrote:
> Hello,
>
> currently, we have a bean
Hello,
currently, we have a bean that is registered for a lot of pages which
holds some information that is only releveant for the scope of the
request. So I thought it woule be more appropriate to make an ASO out of
it with scope request (which does not exist). The reason behind this is
the fact,
