[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tapestry-user
Subject:    Re: Over Reliance on Session Storage
From:       Luke Wilson-Mawer <lukewilsonmawer () gmail ! com>
Date:       2014-04-15 13:58:25
Message-ID: CAKmH+jqwVjk3H27Lu=3Kf6iky1MAJoSDySMbtwn19sK7bSnHkw () mail ! gmail ! com
[Download RAW message or body]


On Tue, Apr 15, 2014 at 2:31 PM, Thiago H de Paula Figueiredo <
thiagohp@gmail.com> wrote:

> On Tue, 15 Apr 2014 07:48:47 -0300, Luke Wilson-Mawer <
> lukewilsonmawer@gmail.com> wrote:
>
>  A slightly more significant departure might be to start replacing your
>> pages and components with stateless rest endpoints using Tynamo's
>> tapestry-resteasy, a piece at a time. We've done this with a couple of
>> our components, moving them into angularjs.
>>
>
> This is a webapp rewrite almost from scratch (at least the web UI part)
> and doesn't really solve the problem of over-reliance on session storage.


Yeah that's completely true, it is basically a rewrite apart from the
service layer but it would solve scaling issues around keeping state in the
session by moving the state to the client.

However, I'm sure there are plenty of ways you can solve the issue without
doing this.


>
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>


[prev in list] [next in list] [prev in thread] [next in thread]