com/Session-creation-with-stateless-pages-in-Chrome-tp4659106p4659122.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
That's the problem. Session.bind() isn't called. I put a breakpoin in
AbstractHttpSessionStore.bind() but still it's hard to tell what's causing
this to be called...
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Session-creation-with-state
Op 28-5-2013 15:59, schreef ChambreNoire:
How would I check this? I disabled "Predict network actions to improve page
load performance" but that hasn't changed anything.
Thanks
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Session-creation-wit
How would I check this? I disabled "Predict network actions to improve page
load performance" but that hasn't changed anything.
Thanks
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Session-creation-with-stateless-pages-in-Chrome-tp4659106p4659111
suppose could always move this
pageparameter extraction into the various stateless pages which need these
parameters (and thus duplicate it) however I'd like to know why on earth
this happens exclusively with Google Chrome (in case it's symptomatic of
some other undetected problem).
various reasons
I have opted to extract cetain pageparameters within the wicket session
constructor, this is problematic. I suppose could always move this
pageparameter extraction into the various stateless pages which need these
parameters (and thus duplicate it) however I'd like to know w
Thanks for your quick response, guys! Got it working. No session expired
message for now.
Very helpful was the hint on how to decide between new/expired session but
also the general information about stateless-ness.
And your guide is awesome, Andrea! Can't believe I didn't run across this
earlier
For a brief introduction to stateless vs stateful pages you can read
chapter 6 of free guide:
http://code.google.com/p/wicket-guide/
Hey there, i'm currently trying to understand what is actually needed so
Wicket considers a page stateful. Could you provide me some basic
information on that?
B
Hi,
On Wed, May 15, 2013 at 4:16 PM, Benedikt Schlegel wrote:
> Hey there, i'm currently trying to understand what is actually needed so
> Wicket considers a page stateful. Could you provide me some basic
> information on that?
>
A Page is stateless by default. It becomes stateful when:
- you
Hey there, i'm currently trying to understand what is actually needed so
Wicket considers a page stateful. Could you provide me some basic
information on that?
Basically, I want the user to authorize for the application and if he's
not, he should be send back to the login page. In the case of sess
Phillips - USAA
> >
> > -Original Message-
> > From: René Vangsgaard [mailto:rene.vangsga...@gmail.com]
> > Sent: Monday, December 10, 2012 3:29 PM
> > To: users@wicket.apache.org
> > Subject: EXTERNAL: stateless pages
> >
> > I am looking into stateless
may ask, what is it about statefulness that concerns you?
>
> Thanks,
> -David Phillips - USAA
>
> -Original Message-
> From: René Vangsgaard [mailto:rene.vangsga...@gmail.com]
> Sent: Monday, December 10, 2012 3:29 PM
> To: users@wicket.apache.org
> Subject: EXTERNA
llips - USAA
-Original Message-
From: René Vangsgaard [mailto:rene.vangsga...@gmail.com]
Sent: Monday, December 10, 2012 3:29 PM
To: users@wicket.apache.org
Subject: EXTERNAL: stateless pages
I am looking into stateless wicket. Do the setStatelessHint() work as expected?
My links are gene
I am looking into stateless wicket. Do the setStatelessHint() work as
expected? My links are generated correctly, but when the page is rendered a
?#number is rendered - the #number being the "normal wicket counter". I
read that the presence of this number indicates my page is not stateless.
And it
Steffens
wrote:
> Hi,
>
> I have a bunch of stateless pages, each calling setStatelessHint(true) in
> the constructor to indicate this. I've now noticed that when one of these
> pages calls setResponsePage, the target page is always considered
> stateful, since Reque
Hi,
I have a bunch of stateless pages, each calling setStatelessHint(true) in
the constructor to indicate this. I've now noticed that when one of these
pages calls setResponsePage, the target page is always considered
stateful, since RequestCycle#setResponsePage explicitly resets the hint.
Heigl wrote:
> > Hello,
> >
> > I'm currently in the process of migrating a largish Wicket 1.4 application
> > to 1.5. When moving from 1.5.5 to 1.5.6 something related to feedback
> > messages breaks.
> >
> > On all my stateless pages, feedbac
edback
> messages breaks.
>
> On all my stateless pages, feedback messages are not rendered anymore when
> using:
>
> @Override
> protected void onError(AjaxRequestTarget target, Form form) {
> target.addChildren(MyForm.this, FeedbackPanel.class);
> }
>
> The form is
Hello,
I'm currently in the process of migrating a largish Wicket 1.4 application
to 1.5. When moving from 1.5.5 to 1.5.6 something related to feedback
messages breaks.
On all my stateless pages, feedback messages are not rendered anymore when
using:
@Override
protected void on
Just call Session.get().bind() after successful login.
On Tue, Feb 21, 2012 at 11:04 AM, Sergej Sizov
wrote:
> Hi,
>
>
>
> I have a web application that contains only stateless pages. I need to allow
> users to register and login. So I need to store user's login in a ses
Hi,
I have a web application that contains only stateless pages. I need to allow
users to register and login. So I need to store user's login in a session.
Could you please advise me how to start session after successful login and
make session persistent for stateless pages?
Any lin
stateless ones. If I mount my stateless pages in
> my application, does this override the session creation? (My stateless pages
> are the homepage, login page, faq etc).
the session is created to keep the encryption key the strategy uses.
-igor
>
> Second, I occasionally see the following er
gt; >> > AFAICS, everything else is the same as in the request before.
> > >> >
> > >> > Is it possible _not_ to modify the Session.pageIdCounter if the page is
> > >> > really stateless (or just don't invoke Page.setNextAvailableId())
f the page is
> >> > really stateless (or just don't invoke Page.setNextAvailableId())?
> >> >
> >> > I'm interested in this, as I'm just implementing a feature for the
> >> > memcached-session-manager ([1], memcached based session re
it possible _not_ to modify the Session.pageIdCounter if the page is
>> > really stateless (or just don't invoke Page.setNextAvailableId())?
>> >
>> > I'm interested in this, as I'm just implementing a feature for the
>> > memcached-session-manager
7;m just implementing a feature for the
> > memcached-session-manager ([1], memcached based session replication),
> > which checks if session data has changed and replicates sessions only if
> > this is provided. If session data did not change, the replication is
> > omitte
patches are always welcome.
-igor
On Thu, Mar 11, 2010 at 1:23 PM, wrote:
> From my basic understanding I'd say that for stateless pages nothing should
> depend on the pageId. What do you think about incrementing the pageId when
> it's first accessed? I'd like to crea
>From my basic understanding I'd say that for stateless pages nothing should
>depend on the pageId. What do you think about incrementing the pageId when
>it's first accessed? I'd like to create a patch for it to see if this works.
Cheers,
Martin
-- Urspr. Mitt. --
Betr
d. Therefore, if the Session.pageIdCounter would be left unchanged
> for stateless pages, this would allow to make use of this feature in
> wicket apps.
>
> Thanx && cheers,
> Martin
>
>
> [1] http://code.google.com/p/memcached-session-manager/
>
>
&
t unchanged
for stateless pages, this would allow to make use of this feature in
wicket apps.
Thanx && cheers,
Martin
[1] http://code.google.com/p/memcached-session-manager/
signature.asc
Description: This is a digitally signed message part
> > > > > possible.
> > > > >
> > > > > Cheers,
> > > > > Martin
> > > > >
> > > > >
> > > > > On Fri, 2009-04-17 at 14:55 -0700, Igor Vaynberg wrote:
> > > > >> you cannot use
>> what you can do is write javascript yourself using jquery, or
> > > >> something else to perform an ajax callback to some url you control and
> > > >> then replace some markup on your page with returned markup.
> > > >>
> > > >> -igor
> >
> >>
> > >> On Fri, Apr 17, 2009 at 2:52 PM, Martin Grotzke
> > >> wrote:
> > >> > Hello,
> > >> >
> > >> > can somebody help with this?
> > >> >
> > >> > Thanx && cheers,
> >
t; can somebody help with this?
> >> >
> >> > Thanx && cheers,
> >> > Martin
> >> >
> >> >
> >> > On Mon, 2009-04-13 at 12:16 +0200, martin.grot...@javakaffee.de wrote:
> >> >> Hi,
> >> >
; cheers,
>> > Martin
>> >
>> >
>> > On Mon, 2009-04-13 at 12:16 +0200, martin.grot...@javakaffee.de wrote:
>> >> Hi,
>> >>
>> >> I'm currently evaluating how it's possible to have stateless pages with
>> >>
9-04-13 at 12:16 +0200, martin.grot...@javakaffee.de wrote:
> >> Hi,
> >>
> >> I'm currently evaluating how it's possible to have stateless pages with
> >> some information loaded asynchronously via AJAX.
> >>
> >> I found these postin
t; Hi,
>>
>> I'm currently evaluating how it's possible to have stateless pages with
>> some information loaded asynchronously via AJAX.
>>
>> I found these postings that are somehow related to this
>> http://www.nabble.com/Stateless-AJAX-links-td2003130
Hello,
can somebody help with this?
Thanx && cheers,
Martin
On Mon, 2009-04-13 at 12:16 +0200, martin.grot...@javakaffee.de wrote:
> Hi,
>
> I'm currently evaluating how it's possible to have stateless pages with
> some information loaded asynchronously via AJA
Hi,
I'm currently evaluating how it's possible to have stateless pages with
some information loaded asynchronously via AJAX.
I found these postings that are somehow related to this
http://www.nabble.com/Stateless-AJAX-links-td20031309.html
http://www.nabble.com/Directions-for-Stat
In our use case all the pages are stateless, but they are by no means
static. We have in fact designed the entire site to use stateless pages,
again for scalability; but every single page is also dynamic. I would like
to produce and share some metrics from the JVM around object allocation and
On Sun, May 18, 2008 at 11:04 PM, James Carman
<[EMAIL PROTECTED]> wrote:
> stateless != static, though
>
> If you cache the results of a stateless page, you could show stale
> information from the database, correct?
True, so it depends on your use case. And obviously it wouldn't work
for form pro
the /result/ of stateless
> pages.
>
> Regards,
>Erik.
>
>
> Joel Halbert wrote:
>>
>> Hi,
>>
>> I was wondering whether it was possible to implement "pooling" of
>> stateless pages? Possibly using a custom PageMap implementation
> I think it would probably make more sense to cache the /result/ of stateless
> pages.
Yeah, that might make quite the difference. The best place for that
would be a filter, probably defined before the Wicket filter. Tons of
different options as well though. And definitively something I
Hello,
I think it would probably make more sense to cache the /result/ of
stateless pages.
Regards,
Erik.
Joel Halbert wrote:
Hi,
I was wondering whether it was possible to implement "pooling" of stateless pages? Possibly using a custom PageMap implementation?
Although n
---
>> From: "Eelco Hillenius" <[EMAIL PROTECTED]>
>> Sent: Sunday, May 18, 2008 5:58 PM
>> To:
>> Subject: Re: Page pooling (for stateless pages)
>>
>> I was wondering whether it was possible to implement "pooling" of
>>
ot; <[EMAIL PROTECTED]>
> Sent: Sunday, May 18, 2008 5:58 PM
> To:
> Subject: Re: Page pooling (for stateless pages)
>
> I was wondering whether it was possible to implement "pooling" of
>>> stateless pages? Possibly using a custom PageMap implementatio
any metrics that we produce.
Thx,
Joel
--
From: "Eelco Hillenius" <[EMAIL PROTECTED]>
Sent: Sunday, May 18, 2008 5:58 PM
To:
Subject: Re: Page pooling (for stateless pages)
I was wondering whether it was possible to implem
> I was wondering whether it was possible to implement "pooling" of stateless
> pages? Possibly using a custom PageMap implementation?
I think you can just implement the pooling mechanism yourself, and
provide a custom version of IPageFactory (which is to be set in
session settin
On Sun, May 18, 2008 at 9:47 AM, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> do you have a benchmark that shows that pooling is indeed faster?
>
> servlets are pooled because they may require heavy initialization.
> wicket pages are much more lightweight in comparison.
And, the more heavyweight you
ter
> scalability.
>
> Rgs,
> Joel
>
> --
> From: "Johan Compagner" <[EMAIL PROTECTED]>
> Sent: Sunday, May 18, 2008 12:27 PM
> To:
> Subject: Re: Page pooling (for stateless pages)
>
>> For stateless
t; --
>> From: "Johan Compagner" <[EMAIL PROTECTED]>
>> Sent: Sunday, May 18, 2008 12:27 PM
>> To:
>> Subject: Re: Page pooling (for stateless pages)
>>
>>
>>
>> > For stateless pages
Sent: Sunday, May 18, 2008 12:27 PM
> To:
> Subject: Re: Page pooling (for stateless pages)
>
>
>
> > For stateless pages??
> > The whole point of stateless is that they arent kept in the
> session/memory.
> >
> > And pooling pages is not really what yo
nt, so long as they
are all young gen objects. And with parallel gc this should result in
minimal effect on an application.
--
From: "Martijn Dashorst" <[EMAIL PROTECTED]>
Sent: Sunday, May 18, 2008 12:42 PM
To:
Subject: Re: Page pool
s
> Servlets.
> It is also the a technique used by Tapestry 5 to achieve greater
> scalability.
>
> Rgs,
> Joel
>
> --
> From: "Johan Compagner" <[EMAIL PROTECTED]>
> Sent: Sunday, May 18, 2008 12:2
be implemented.
I noted that Tapestry 5 has chosen to implement stateless pages and pooling
of these by default.
--
From: "Matej Knopp" <[EMAIL PROTECTED]>
Sent: Sunday, May 18, 2008 12:25 PM
To:
Subject: Re: Page pooling (for
ity.
Rgs,
Joel
--
From: "Johan Compagner" <[EMAIL PROTECTED]>
Sent: Sunday, May 18, 2008 12:27 PM
To:
Subject: Re: Page pooling (for stateless pages)
For stateless pages??
The whole point of stateless is that they arent kept in
For stateless pages??
The whole point of stateless is that they arent kept in the session/memory.
And pooling pages is not really what you want any way, you can only
pool then for a single user/sessiion so you would have a pool for
every session.
And when do you decide to return a pooled page
For stateless pages??
The whole point of stateless is that they arent kept in the session/memory.
And pooling pages is not really what you want any way, you can only
pool then for a single user/sessiion so you would have a pool for
every session.
And when do you decide to return a pooled page
Hi,
first of all, I don't really think it's worth pooling pages. I can't
imagine that page instance creation would have that much overhead.
Also stateless pages doesn't mean they don't contain any state. The
page is stateless because it's not kept between requests,
Hi,
I was wondering whether it was possible to implement "pooling" of stateless
pages? Possibly using a custom PageMap implementation?
Although newer JVM's are good at performing GC, pooling is a reasonable
additional technique to use for achieving that extra bit of scalabil
el on your blog once.
> unfortunately it seems to be gone. is this still floating around anywhere?
>
> thx uwe
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PRO
Jonathan Locke schrieb:
hi Jonathan
Until you've got a handle on your scaling problem (and it
probably is that and not a performance problem) and you know what needs to
be tuned, the best policy is probably to just build something simply and
quickly in order to discover if you even have a proble
y and
quickly in order to discover if you even have a problem that requires this
solution.
Martijn Lindhout wrote:
>
> Hi guys,
>
> In the release notes, I read: "stateless pages and components for those
> parts of your application that needs to scale to extremely large numbers
On Jan 19, 2008 5:18 AM, Martijn Lindhout <[EMAIL PROTECTED]> wrote:
> Hi guys,
>
> In the release notes, I read: "stateless pages and components for those
> parts of your application that needs to scale to extremely large numbers of
> users".
>
> Does somebod
Hi guys,
In the release notes, I read: "stateless pages and components for those
parts of your application that needs to scale to extremely large numbers of
users".
Does somebody use this feature or is it somewhere documented? What do I have
to do and what are the differences from
there
any other solution or any pattern to implement this issue better?
Thanks
fatih
--
View this message in context:
http://www.nabble.com/Ajax-History-Back-support-on-Stateless-pages-tp14556855p14556855.html
Sent from the Wicket - User mailing list archive at Nabble.com
://www.nabble.com/Ajax-History-Back-support-on-Stateless-pages-tp14556855p14556855.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
67 matches
Mail list logo
