tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mindbridge" <mindbridge...@yahoo.com>
Subject Re: problem: how to avoid inconsistencies when a user open a linkin anew window
Date Thu, 05 Jun 2003 06:56:04 GMT
Hi,

    From what I can see, you want the persistent page properties (perhaps
only some of them) to be stored as part of the URL -- this will make things
work in the context you describe. We've been thinking about how to possibly
realize this, but it is tricky, and at the very least will require
JavaScript once you have more data to pass this way because of the
limitations on URL size. (you can check the archives of this list -- the
topic was storing data in cookies). Unfortunately, this is not currently
supported and there have been thoughts of not locking the page recorders at
the beginning of rendering, which would close this avenue altogether...

    Personally, I am not very sure that what you describe is a very big
problem, but having the ability to put only certain persistent properties in
the request (while the rest can be in the session) is somethings that has
popped up a number of times. Perhaps there is some wisdom in implementing
this after all. My only big problem is that possible JavaScript
dependency...

Best regards,
-mb

----- Original Message ----- 
From: "Marilen Corciovei" <len@nemesisit.rdsnet.ro>
To: "Tapestry development" <tapestry-dev@jakarta.apache.org>
Cc: <hlship@attbi.com>
Sent: Thursday, June 05, 2003 4:51 AM
Subject: RE: problem: how to avoid inconsistencies when a user open a linkin
anew window


> On Thu, 2003-06-05 at 01:47, Howard M. Lewis Ship wrote:
> > Do you have a specific issue that prevents you from using persistent
page properties?
> >
>
> Take this case: I have a dynamic category, products hierarchy. I then
> visit a page showing the categories and select one category in a page
> (shift-click) and another in other page (shift-click). Both pages will
> show the products for the category received as parameter. Can this be a
> persistent page property. As far as I know both pages share the save
> httpSession managed by a cookie. Assume then each page will have a
> number of contained components for instance a table. This will contain a
> direct link for sort. What happens it I store the category as a
> persistent page property, load page1, load page2 and the click to sort
> page1. I guess page1 will now show the sorted items in page2.
>
> the sequence is as follows:
>
> - load page1 in a new page with a parameter C1, store C1 in session
> - load page2 in a new page with a parameter C2, store C2 in session
> - click on page1 directLink
> - render page1 using C2 from session ?!
>
> Am I in mistake?
> Len
>
> My ideea is to write a directService that takes the original param C1
> when creating the gesture and embeds it in the link parameters.
>
>
>
> > --
> > Howard M. Lewis Ship
> > Creator, Tapestry: Java Web Components
> > http://jakarta.apache.org/tapestry
> >
> >
> >
> > > -----Original Message-----
> > > From: Marilen Corciovei [mailto:len@nemesisit.rdsnet.ro]
> > > Sent: Wednesday, June 04, 2003 11:24 AM
> > > To: tapestry-dev@jakarta.apache.org
> > > Subject: problem: how to avoid inconsistencies when a user
> > > open a link in anew window
> > >
> > >
> > > I posted this problem on the user group but I now think this
> > > is more of a developer nature. Maybe here can someone help.
> > >
> > > assume I have a page which gets some parameters, it uses them
> > > to render itself. The page also contains a table component.
> > > When the user clicks a table column which is a DirectLink
> > > this one will call the page again but with the original
> > > parameters lost. I am trying to find a way not to be forced
> > > to modify the table column to send the original parameters
> > > also. I was thinking of extending DirectService. I know how
> > > to handle parameter sending with my own links but not with
> > > others from existing components and I hope not to rewrote them.
> > >
> > > Len
> > >
> > > On Wed, 2003-06-04 at 17:11, Bill Lear wrote:
> > > > On , June 4, 2003 at 16:49:14 (+0300) Marilen Corciovei writes:
> > > > >I am having problem with users opening a link in a new window. I
> > > tried
> > > > >to store specific navigation data in the visit but this result in
> > > > >inconsistencies. My ideea was to make all the links carry some data
> > > as
> > > > >parameters. Can this be done in some way without modifind every
> > > > >component?
> > >
> > > -- 
> > > Marilen Corciovei <len@nemesisit.rdsnet.ro>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> -- 
> Marilen Corciovei <len@nemesisit.rdsnet.ro>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


Mime
View raw message