default == 5
oldest used will be removed.
johan
On 4/15/06,
Eelco Hillenius <[EMAIL PROTECTED]> wrote:
We don't. But we know (or should be able to know) how many pagemaps
were created.
I think what we need is to be able to set a limit on automatically
created pagemaps, and a decent, configurable error page that is
displayed in case that limit is exceeded.
Eelco
On 4/15/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
> how do you know how many windows are open?
>
> johan
>
>
>
> On 4/15/06, Eelco Hillenius <[EMAIL PROTECTED] > wrote:
> >
> Hi Juergen,
>
> What we're trying to solve here is actually slightly different. What
> that code - which has seen a few iterations now - is trying to do is
> to make Wicket operate nicely even when users open multiple windows
> with the same session (like pressing ctrl+n in the browser).
>
> The inability to do this is commonly pointed out as a weakness for
> statefull/ component based frameworks. Usually this is circumvented by
> applying client side state saving in some form. We don't support this
> for various reasons - we might someday, though I think most of us
> doubt whether the disadvantages (like increased processor and bandwith
> utilization and having to rely on POST and _javascript_ for links) weigh
> up against the advantages (unlimited undo/ back button support and
> 'guaranteed' multi window support that scales lineary).
>
> That checking code in WebPage you are refering to now, seems to be
> quite a robust - though not perfect - transparent solution for
> handling multiple windows and tabs.
>
> It could probably use some cleanup and we should define the
> constraints better and give a clear but user friendly exception (page)
> when the constraints are violated (like more than, say, three windows
> open for the same session). It's a lot better than no support at all
> imo.
>
> Eelco
>
> On 4/15/06, Juergen Donnerstag < [EMAIL PROTECTED]> wrote:
> > WebPage now contains quite some code related to popup windows. From
> > what I see there are web apps which require that support, hence we
> > should support it, but it is a limited number. I wonder if it would
> > make sense to move that code into something like PopupWebPage in order
> > not to blur WebPage. And 2nd, but that I guess is my gut feeling, I
> > don't like that we generate _javascript_ for each webpage even though it
> > is never required in my apps.
> >
> > Juergen
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> > that extends applications into web and mobile media. Attend the live
> webcast
> > and join the prime developer group breaking into this new coding
> territory!
> >
> http://sel.as-us.falkag.net/sel?cmdlnk&kid0944&bid$1720&dat1642
> > _______________________________________________
> > Wicket-develop mailing list
> > [email protected]
> >
> https://lists.sourceforge.net/lists/listinfo/wicket-develop
> >
>
>
> -------------------------------------------------------
>
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmdlnk&kid0944&bid$1720&dat1642
> _______________________________________________
> Wicket-develop mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wicket-develop
>
>
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmdlnk&kid0944&bid$1720&dat1642
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
