You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Andrea Chiumenti <ki...@gmail.com> on 2007/04/04 16:23:47 UTC

Difference between an IPage and a IExternalPage

Hi!

Can someone briefly explain why an IExternalPage is bookmarkeable while an
IPage not ?

kiuma

Re: Difference between an IPage and a IExternalPage

Posted by Andrea Chiumenti <ki...@gmail.com>.
Thx for explanation, at this point the question is: why the Tap. disign
differentiates IPage and IExternalPage?

On 4/5/07, Sam Gendler <sg...@ideasculptor.com> wrote:
>
> An IPage is bookmarkable, so long as you just want to bookmark the
> default state of the page when rendered by the page service.  However,
> if you submit a form on that page and then want to bookmark the
> resulting page, you won't be able to, since the form submit will go
> back to your original page, but the rendered results may well be some
> other page entirely, if you activated some other page, or it will be
> the original page in a non-default state.  There is no mechanism to
> pass information about the state you want the page to be in available
> to a standard IPage.  The IExternalPage interface provides you with a
> mechanism to include information about the expected state of the page
> when it loads - for instance, the id of an object, so you can bookmark
> the URL which includes the id, which will enable you to go back to
> that very same page.  The equivalent mechansim for an IPage would
> require rendering the page, then submitting a form containing the id
> in order to load the object, and then render the resulting page.
> There is no obvious or well defined mechanism for putting parameters
> in the URL to the page service in order to load a page in the same
> state it would be in after some listener has fired.
>
> --sam
>
> On 4/4/07, Andrea Chiumenti <ki...@gmail.com> wrote:
> > Hi!
> >
> > Can someone briefly explain why an IExternalPage is bookmarkeable while
> an
> > IPage not ?
> >
> > kiuma
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>

Re: Difference between an IPage and a IExternalPage

Posted by Sam Gendler <sg...@ideasculptor.com>.
An IPage is bookmarkable, so long as you just want to bookmark the
default state of the page when rendered by the page service.  However,
if you submit a form on that page and then want to bookmark the
resulting page, you won't be able to, since the form submit will go
back to your original page, but the rendered results may well be some
other page entirely, if you activated some other page, or it will be
the original page in a non-default state.  There is no mechanism to
pass information about the state you want the page to be in available
to a standard IPage.  The IExternalPage interface provides you with a
mechanism to include information about the expected state of the page
when it loads - for instance, the id of an object, so you can bookmark
the URL which includes the id, which will enable you to go back to
that very same page.  The equivalent mechansim for an IPage would
require rendering the page, then submitting a form containing the id
in order to load the object, and then render the resulting page.
There is no obvious or well defined mechanism for putting parameters
in the URL to the page service in order to load a page in the same
state it would be in after some listener has fired.

--sam

On 4/4/07, Andrea Chiumenti <ki...@gmail.com> wrote:
> Hi!
>
> Can someone briefly explain why an IExternalPage is bookmarkeable while an
> IPage not ?
>
> kiuma
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org