You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by jan_bar <he...@yahoo.com> on 2007/10/03 19:25:02 UTC
Out of order requests
Hi,
I have some troubles with Wicket 1.2.6. I have two pages, pageA has
Image(s), pageB has Flash that talks back to wicket. Here is a trace of HTTP
requests:
pageA - HTML is sent to client
page.image(s) - images are send to client
pageB - HTML is sent to client
pageB.flash - flash starts it's background requests
pageA - now I switch back to pageA via pageB.Link
pageB.flash - flash on pageB still lives and sends request to wicket, this
is the source of trouble
pageA.images - images on pageA doesn't exist, because "session expired"
The trouble is that Flash still "lives" even when new page is loaded into
client. The request from flash seems to confuse wicket. How can I fix this
problem?
Thanks, Jan
--
Jan Bares
http://jan.vegetband.cz
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Out of order requests
Posted by Johan Compagner <jc...@gmail.com>.
yes and that can't be fixed as easy (in 1.2)
Because that would mean that is not an access stack anymore...
for example if you have a stack or only 3.
And you go back once, do a refresh click on something and then again 2 times
back
if we wouldn't have the access stack like now page expired would happen.
Its just a bit tricky. And i dont know if we should really try to fix that
for 1.2
Because what you want then is something like a last acccessed page map.
But that map can't be to small because then page expired could happen a lot
when people
use the back button a lot.
On 10/21/07, Matej Knopp <ma...@gmail.com> wrote:
>
> I believe the problem is accessstackpagemap removing pages too eagerly.
>
> -Matej
>
> On 10/20/07, Johan Compagner <jc...@gmail.com> wrote:
> > me?:)
> > the problem is not easily fixable in 1.2
> > or you have to make sure that the flash is loaded in one page with its
> > own pagemap.
> > 1.3 doesnt have this problem.
> >
> > On 10/20/07, Matej Knopp <ma...@gmail.com> wrote:
> > > Johan?
> > >
> > > -Matej
> > >
> > > On 10/20/07, jan_bar <he...@yahoo.com> wrote:
> > > > Hi,
> > > >
> > > > my question was probably unclear, I will try to post more details:
> > > >
> > > > When I leave a page, let's say id=40, wicket gets request to render
> new
> > > page
> > > > id=41 but flash on previous page still lives and send request to
> wicket
> > > > (this is the souce of troubles). This request from flash is bound to
> page
> > > id
> > > > = 40 and causes wicket to think, that user pressed back button on
> the page
> > > > id=41, so the page id=41 is removed from accessStack. Browser then
> renders
> > > > page id = 41 and send requests for components like pictures etc, but
> since
> > > > page id=41 was removed, all requests return "session expired".
> > > >
> > > > How can I fix this problem?
> > > > (wicket 1.2.6)
> > > >
> > > > Many thanks, Jan
> > > >
> > > > --
> > > > Jan Bares
> > > > http://jan.vegetband.cz
> > > >
> > > >
> > > > "jan_bar" <he...@yahoo.com> wrote in message
> > > > news:fe0j9e$k2v$1@sea.gmane.org...
> > > > > Hi,
> > > > >
> > > > > I have some troubles with Wicket 1.2.6. I have two pages, pageA
> has
> > > > > Image(s), pageB has Flash that talks back to wicket. Here is a
> trace of
> > > > HTTP
> > > > > requests:
> > > > >
> > > > > pageA - HTML is sent to client
> > > > > page.image(s) - images are send to client
> > > > > pageB - HTML is sent to client
> > > > > pageB.flash - flash starts it's background requests
> > > > > pageA - now I switch back to pageA via pageB.Link
> > > > > pageB.flash - flash on pageB still lives and sends request to
> wicket,
> > > this
> > > > > is the source of trouble
> > > > > pageA.images - images on pageA doesn't exist, because "session
> expired"
> > > > >
> > > > > The trouble is that Flash still "lives" even when new page is
> loaded
> > > into
> > > > > client. The request from flash seems to confuse wicket. How can I
> fix
> > > this
> > > > > problem?
> > > > >
> > > > > Thanks, Jan
> > > > >
> > > > > --
> > > > > Jan Bares
> > > > > http://jan.vegetband.cz
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Out of order requests
Posted by jan_bar <he...@yahoo.com>.
Thanks for your support,
the problem is in PageMap.access():
...
// Remove whole page
remove(topPage);
Jan
--
Jan Bares
http://jan.vegetband.cz
"Matej Knopp" <ma...@gmail.com> wrote in message
news:109027740710210706w399cb4a4n30398fd67256caa8@mail.gmail.com...
> I believe the problem is accessstackpagemap removing pages too eagerly.
>
> -Matej
>
> On 10/20/07, Johan Compagner <jc...@gmail.com> wrote:
> > me?:)
> > the problem is not easily fixable in 1.2
> > or you have to make sure that the flash is loaded in one page with its
> > own pagemap.
> > 1.3 doesnt have this problem.
> >
> > On 10/20/07, Matej Knopp <ma...@gmail.com> wrote:
> > > Johan?
> > >
> > > -Matej
> > >
> > > On 10/20/07, jan_bar <he...@yahoo.com> wrote:
> > > > Hi,
> > > >
> > > > my question was probably unclear, I will try to post more details:
> > > >
> > > > When I leave a page, let's say id=40, wicket gets request to render
new
> > > page
> > > > id=41 but flash on previous page still lives and send request to
wicket
> > > > (this is the souce of troubles). This request from flash is bound to
page
> > > id
> > > > = 40 and causes wicket to think, that user pressed back button on
the page
> > > > id=41, so the page id=41 is removed from accessStack. Browser then
renders
> > > > page id = 41 and send requests for components like pictures etc, but
since
> > > > page id=41 was removed, all requests return "session expired".
> > > >
> > > > How can I fix this problem?
> > > > (wicket 1.2.6)
> > > >
> > > > Many thanks, Jan
> > > >
> > > > --
> > > > Jan Bares
> > > > http://jan.vegetband.cz
> > > >
> > > >
> > > > "jan_bar" <he...@yahoo.com> wrote in message
> > > > news:fe0j9e$k2v$1@sea.gmane.org...
> > > > > Hi,
> > > > >
> > > > > I have some troubles with Wicket 1.2.6. I have two pages, pageA
has
> > > > > Image(s), pageB has Flash that talks back to wicket. Here is a
trace of
> > > > HTTP
> > > > > requests:
> > > > >
> > > > > pageA - HTML is sent to client
> > > > > page.image(s) - images are send to client
> > > > > pageB - HTML is sent to client
> > > > > pageB.flash - flash starts it's background requests
> > > > > pageA - now I switch back to pageA via pageB.Link
> > > > > pageB.flash - flash on pageB still lives and sends request to
wicket,
> > > this
> > > > > is the source of trouble
> > > > > pageA.images - images on pageA doesn't exist, because "session
expired"
> > > > >
> > > > > The trouble is that Flash still "lives" even when new page is
loaded
> > > into
> > > > > client. The request from flash seems to confuse wicket. How can I
fix
> > > this
> > > > > problem?
> > > > >
> > > > > Thanks, Jan
> > > > >
> > > > > --
> > > > > Jan Bares
> > > > > http://jan.vegetband.cz
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Out of order requests
Posted by Matej Knopp <ma...@gmail.com>.
I believe the problem is accessstackpagemap removing pages too eagerly.
-Matej
On 10/20/07, Johan Compagner <jc...@gmail.com> wrote:
> me?:)
> the problem is not easily fixable in 1.2
> or you have to make sure that the flash is loaded in one page with its
> own pagemap.
> 1.3 doesnt have this problem.
>
> On 10/20/07, Matej Knopp <ma...@gmail.com> wrote:
> > Johan?
> >
> > -Matej
> >
> > On 10/20/07, jan_bar <he...@yahoo.com> wrote:
> > > Hi,
> > >
> > > my question was probably unclear, I will try to post more details:
> > >
> > > When I leave a page, let's say id=40, wicket gets request to render new
> > page
> > > id=41 but flash on previous page still lives and send request to wicket
> > > (this is the souce of troubles). This request from flash is bound to page
> > id
> > > = 40 and causes wicket to think, that user pressed back button on the page
> > > id=41, so the page id=41 is removed from accessStack. Browser then renders
> > > page id = 41 and send requests for components like pictures etc, but since
> > > page id=41 was removed, all requests return "session expired".
> > >
> > > How can I fix this problem?
> > > (wicket 1.2.6)
> > >
> > > Many thanks, Jan
> > >
> > > --
> > > Jan Bares
> > > http://jan.vegetband.cz
> > >
> > >
> > > "jan_bar" <he...@yahoo.com> wrote in message
> > > news:fe0j9e$k2v$1@sea.gmane.org...
> > > > Hi,
> > > >
> > > > I have some troubles with Wicket 1.2.6. I have two pages, pageA has
> > > > Image(s), pageB has Flash that talks back to wicket. Here is a trace of
> > > HTTP
> > > > requests:
> > > >
> > > > pageA - HTML is sent to client
> > > > page.image(s) - images are send to client
> > > > pageB - HTML is sent to client
> > > > pageB.flash - flash starts it's background requests
> > > > pageA - now I switch back to pageA via pageB.Link
> > > > pageB.flash - flash on pageB still lives and sends request to wicket,
> > this
> > > > is the source of trouble
> > > > pageA.images - images on pageA doesn't exist, because "session expired"
> > > >
> > > > The trouble is that Flash still "lives" even when new page is loaded
> > into
> > > > client. The request from flash seems to confuse wicket. How can I fix
> > this
> > > > problem?
> > > >
> > > > Thanks, Jan
> > > >
> > > > --
> > > > Jan Bares
> > > > http://jan.vegetband.cz
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > >
> > > >
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Out of order requests
Posted by Johan Compagner <jc...@gmail.com>.
me?:)
the problem is not easily fixable in 1.2
or you have to make sure that the flash is loaded in one page with its
own pagemap.
1.3 doesnt have this problem.
On 10/20/07, Matej Knopp <ma...@gmail.com> wrote:
> Johan?
>
> -Matej
>
> On 10/20/07, jan_bar <he...@yahoo.com> wrote:
> > Hi,
> >
> > my question was probably unclear, I will try to post more details:
> >
> > When I leave a page, let's say id=40, wicket gets request to render new
> page
> > id=41 but flash on previous page still lives and send request to wicket
> > (this is the souce of troubles). This request from flash is bound to page
> id
> > = 40 and causes wicket to think, that user pressed back button on the page
> > id=41, so the page id=41 is removed from accessStack. Browser then renders
> > page id = 41 and send requests for components like pictures etc, but since
> > page id=41 was removed, all requests return "session expired".
> >
> > How can I fix this problem?
> > (wicket 1.2.6)
> >
> > Many thanks, Jan
> >
> > --
> > Jan Bares
> > http://jan.vegetband.cz
> >
> >
> > "jan_bar" <he...@yahoo.com> wrote in message
> > news:fe0j9e$k2v$1@sea.gmane.org...
> > > Hi,
> > >
> > > I have some troubles with Wicket 1.2.6. I have two pages, pageA has
> > > Image(s), pageB has Flash that talks back to wicket. Here is a trace of
> > HTTP
> > > requests:
> > >
> > > pageA - HTML is sent to client
> > > page.image(s) - images are send to client
> > > pageB - HTML is sent to client
> > > pageB.flash - flash starts it's background requests
> > > pageA - now I switch back to pageA via pageB.Link
> > > pageB.flash - flash on pageB still lives and sends request to wicket,
> this
> > > is the source of trouble
> > > pageA.images - images on pageA doesn't exist, because "session expired"
> > >
> > > The trouble is that Flash still "lives" even when new page is loaded
> into
> > > client. The request from flash seems to confuse wicket. How can I fix
> this
> > > problem?
> > >
> > > Thanks, Jan
> > >
> > > --
> > > Jan Bares
> > > http://jan.vegetband.cz
> > >
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Out of order requests
Posted by Matej Knopp <ma...@gmail.com>.
Johan?
-Matej
On 10/20/07, jan_bar <he...@yahoo.com> wrote:
> Hi,
>
> my question was probably unclear, I will try to post more details:
>
> When I leave a page, let's say id=40, wicket gets request to render new page
> id=41 but flash on previous page still lives and send request to wicket
> (this is the souce of troubles). This request from flash is bound to page id
> = 40 and causes wicket to think, that user pressed back button on the page
> id=41, so the page id=41 is removed from accessStack. Browser then renders
> page id = 41 and send requests for components like pictures etc, but since
> page id=41 was removed, all requests return "session expired".
>
> How can I fix this problem?
> (wicket 1.2.6)
>
> Many thanks, Jan
>
> --
> Jan Bares
> http://jan.vegetband.cz
>
>
> "jan_bar" <he...@yahoo.com> wrote in message
> news:fe0j9e$k2v$1@sea.gmane.org...
> > Hi,
> >
> > I have some troubles with Wicket 1.2.6. I have two pages, pageA has
> > Image(s), pageB has Flash that talks back to wicket. Here is a trace of
> HTTP
> > requests:
> >
> > pageA - HTML is sent to client
> > page.image(s) - images are send to client
> > pageB - HTML is sent to client
> > pageB.flash - flash starts it's background requests
> > pageA - now I switch back to pageA via pageB.Link
> > pageB.flash - flash on pageB still lives and sends request to wicket, this
> > is the source of trouble
> > pageA.images - images on pageA doesn't exist, because "session expired"
> >
> > The trouble is that Flash still "lives" even when new page is loaded into
> > client. The request from flash seems to confuse wicket. How can I fix this
> > problem?
> >
> > Thanks, Jan
> >
> > --
> > Jan Bares
> > http://jan.vegetband.cz
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Out of order requests
Posted by jan_bar <he...@yahoo.com>.
Hi,
my question was probably unclear, I will try to post more details:
When I leave a page, let's say id=40, wicket gets request to render new page
id=41 but flash on previous page still lives and send request to wicket
(this is the souce of troubles). This request from flash is bound to page id
= 40 and causes wicket to think, that user pressed back button on the page
id=41, so the page id=41 is removed from accessStack. Browser then renders
page id = 41 and send requests for components like pictures etc, but since
page id=41 was removed, all requests return "session expired".
How can I fix this problem?
(wicket 1.2.6)
Many thanks, Jan
--
Jan Bares
http://jan.vegetband.cz
"jan_bar" <he...@yahoo.com> wrote in message
news:fe0j9e$k2v$1@sea.gmane.org...
> Hi,
>
> I have some troubles with Wicket 1.2.6. I have two pages, pageA has
> Image(s), pageB has Flash that talks back to wicket. Here is a trace of
HTTP
> requests:
>
> pageA - HTML is sent to client
> page.image(s) - images are send to client
> pageB - HTML is sent to client
> pageB.flash - flash starts it's background requests
> pageA - now I switch back to pageA via pageB.Link
> pageB.flash - flash on pageB still lives and sends request to wicket, this
> is the source of trouble
> pageA.images - images on pageA doesn't exist, because "session expired"
>
> The trouble is that Flash still "lives" even when new page is loaded into
> client. The request from flash seems to confuse wicket. How can I fix this
> problem?
>
> Thanks, Jan
>
> --
> Jan Bares
> http://jan.vegetband.cz
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org