>
> Why are you asking that? Any specific need?

I'm asking because having a maintained session between the client and the
server is a better scenario. Instead of having to authenticate the user's
credentials upon every request. I'm aware there are other standard methods
to have a statefull web service, but I haven't explored that area yet, and
I thought it could be done faster and easier using the
ApplicationStateManager. Frankly the idea is not fully developed in my head.

Also I always like exploring all possible options to always be free to
chose whatever fit my needs more, and I always like to know more Tapestry
tricks.

I haven't used any other web framework and IoC other than Tapestry and I'm
not planning to do so anytime soon. It's a very good framework and I love
using it. So I'm always trying to find out ways to tweak it in every way
possible.



*---------------------*
*Muhammad Gelbana*
Java Software Engineer


On Fri, Aug 30, 2013 at 6:58 PM, Thiago H de Paula Figueiredo <
thiag...@gmail.com> wrote:

> On Fri, 30 Aug 2013 12:15:00 -0300, Muhammad Gelbana <m.gelb...@gmail.com>
> wrote:
>
>  I have one last question. Is it possible to instruct the
>> ApplicationStateManager to manage it's sessions using something else than
>> a HTTP based request (i.e. Whether its *HttpServletRequest* or Tapestry's *
>> Request*) ?
>>
>
> Tapestry's Request is just a thin layer over HttpServletRequest. Same for
> Session and HttpSession. So, in the end, it's actually the servlet
> container the one implementing the session handling. You can override,
> advise or decorate the ApplicationStateManager and implement it any way you
> want. I never had a situation that needed that. Why are you asking that?
> Any specific need?
>
>
>  This has been fruitful discussion, thanks a lot :)
>>
>
> :)
>
>
> --
> Thiago H. de Paula Figueiredo
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: 
> users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org>
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>

Reply via email to