When you bind a form, you write functions that handle parts of the form. They
are stored in memory and when the form is submitted they are executed. They are
triggered by assigning them a unique id and using it as the form element's
name. There's no way to preserve the functions to survive a res
The ProtoExtendedSession looks like it might match what I'm looking for.
With that, they won't have to re-login, right? We're trying to avoid
multi-page state-full workflows so that is not a problem. Are you saying if
they have a form up, then submit it (say to update a record), that will
fail?
On Mon, Mar 1, 2010 at 1:19 PM, Jeppe Nejsum Madsen wrote:
> Ahh just saw David beat me to it with the other reply :-)
>
> John Pletka writes:
>
> > It is a business application - lots of forms, reports, data lookups. I'm
> > not too concerned about the performance on a single node - at any give
Ahh just saw David beat me to it with the other reply :-)
John Pletka writes:
> It is a business application - lots of forms, reports, data lookups. I'm
> not too concerned about the performance on a single node - at any given time
> we'll probably have a max of 1000 requests a minute coming in
It is a business application - lots of forms, reports, data lookups. I'm
not too concerned about the performance on a single node - at any given time
we'll probably have a max of 1000 requests a minute coming in which I've
seen Lift handle easily. The biggest problem is we need near 100% up-time.
John Pletka writes:
> I was tasked with designing a new web-based application that has the
> requirement of being able to run on multiple servers that could be
> 1) Load balanced without requiring sticky sessions and
> 2) Single nodes could be transparently shutdown or added without the users
> n
On Mon, Mar 1, 2010 at 12:29 PM, John Pletka wrote:
> I was tasked with designing a new web-based application that has the
> requirement of being able to run on multiple servers that could be
> 1) Load balanced without requiring sticky sessions and
> 2) Single nodes could be transparently shutdow
I was tasked with designing a new web-based application that has the
requirement of being able to run on multiple servers that could be
1) Load balanced without requiring sticky sessions and
2) Single nodes could be transparently shutdown or added without the users
noticing
I would like to use Lif
