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.html#Threaded+Service+Model > > They also mention on there how to handle cleanup at the end of the > request with HiveMind's servlet filter and the Discardable interface > if needed. > > On 8/3/07, Christian Haselbach <[EMAIL PROTECTED]> wrote: > > 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 works as I think. > > So the request is done in a new thread, the service is created for this > > thread and is discarded when the request finishes, right? > > > > That would work for me, if this is the way things go. > > > > Regards, > > Christian > > > > -- > > Christian Haselbach - [EMAIL PROTECTED] - +49 176 2082 5804 > > TNG Technology Consulting GmbH, Betastr. 13a, 85774 Unterföhring > > Geschäftsführer: Henrik Klagges, Gerhard Müller, Christoph Stock > > Amtsgericht München, HRB 135082 > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
-- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
