scope="client" would imply that the data is stored on the client (much
like client-side persistent properties, as query parameters and/or
hidden form fields).

I think Richard is right, having ASO data scoped to the current
request might be quite useful; this would be created on first
reference and accessible to all pages and components for the duration
of the request, then discarded.  Creating this would be quite easy. 
Still I'd like to see a JIRA issue and a real use case before
committing to changes for 4.0.

On 10/26/05, Hensley, Richard <[EMAIL PROTECTED]> wrote:
> Henri,
>
> You would probably change the service model to threaded. A threaded hivemind
> service running in an applet container that has the hivemind filter
> configured, or is Tapestry 4, will create a new instance on first request
> from the request, and release the instance at the end of the request.
>
> Richard
>
> -----Original Message-----
> From: Henri Dupre [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 25, 2005 9:15 PM
> To: Tapestry development
> Subject: Re: scope="client" for ApplicationObjects
>
> On 10/25/05, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
> > You might want to check out the SiteMap service here:
> > http://tacos.sourceforge.net/hivemind/SiteMap.html. We use it for
> basically
> > the same that you describe, injecting it wherever we want it.
>
> If I could have one instance of the service per request, this would
> really work for me. How can I do that?
>
> Thanks,
>
> Henri.
>
> ---------------------------------------------------------------------
> 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]
>
>


--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind

Professional Tapestry training, mentoring, support
and project work.  http://howardlewisship.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to