Check. Ok - I wasn't sure about per-thread, since it's possible to
implement thread scope against a request object, instead of per-thread.
thanks,
Christian.
On Jul 16, 2010, at 2:39 PM, Howard Lewis Ship wrote:
per-thread is the same as request within a Tapestry application.
There's been talk about a sesson scope, but it doesn't exist.
SessionState are not services so there's no scope for them.
On Fri, Jul 16, 2010 at 11:30 AM, Christian Edward Gruber
<christianedwardgru...@gmail.com> wrote:
I see singleton and per-thread... and there's an implicit session
scope wiht
SessionState annotations...
Are there "session" and "reqeust" scopes? I've managed to avoid a
request-scoped object until now, but I think I need one in the
ioc... but I
don't see these two scopes explicitly documented anywhere.
Is there a web equivalent to ScopeConstants? Or just well-defined,
documented scope names?
Christian.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
