I could lie and say its about efficiency in memory-deficient devices like cell-phones.
The reality is more about my personal sense of aesthetics; also the more legible URLs are easier for humans, even me, to parse. But I think getting rid of the need for a <base> tag is on overridingly good thing. ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, August 19, 2002 4:59 AM Subject: Re: [Tapestry-developer] new (2.2) URL generation and anchor fragments > I didn't see the need for changing it from what it was before. Also, I am > not sure why the context stuff is best dealt with as an array as opposed to > named params just like the rest (e.g. t_context1...the t_ being used to > reserve it for the framework). All that base URL stuff is spooky. > > > ----- Forwarded by Christian Hall/Technology/Equifax on 08/19/2002 07:59 AM > ----- > |--------+----------------------------------------------> > | | "Howard M. Lewis Ship" | > | | <[EMAIL PROTECTED]> | > | | Sent by: | > | | [EMAIL PROTECTED]| > | | eforge.net | > | | | > | | | > | | 08/19/2002 10:21 AM | > | | | > |--------+----------------------------------------------> > >--------------------------------------------------------------------------- ----------------------| > | | > | To: "Richard Lewis-Shell" <[EMAIL PROTECTED]>, "Tapestry Developer (E-mail)" | > | <[EMAIL PROTECTED]> | > | cc: | > | Subject: Re: [Tapestry-developer] new (2.2) URL generation and anchor fragments | > | | > >--------------------------------------------------------------------------- ----------------------| > > > > Geez ... another nail in the coffin of using pathInfo to (neatly) store > service and parameters. > > I'm now thinking of changing the URL encoding (again!) from: > > /context/servlet/serviceName/context1/context2?sp=param1&sp=param2 > > To: > > /context/servlet?service=serviceName/context1/context2&sp=param1&sp=param2 > > This would eliminate the need for the <base> tag generated by the Shell > component and would allow relative paths to static assets to work properly, > etc., etc. > > ----- Original Message ----- > From: "Richard Lewis-Shell" <[EMAIL PROTECTED]> > To: "Tapestry Developer (E-mail)" > <[EMAIL PROTECTED]> > Sent: Sunday, August 18, 2002 10:53 PM > Subject: [Tapestry-developer] new (2.2) URL generation and anchor fragments > > > > We do this a lot in our app to jump (scroll) around a page: > > > > <a name="top">stuff at top of page goes here</a> > > > > then to get back to the top of the page: > > <a href="#top">top</a> > > > > Note - this is all static - no server side generation required. > > > > Before 2.2 this worked fine. But now Tapestry puts a <base > > href="http://localhost/webapp/myapp";> tag in the page so the relative > href > > gets interpreted (by the browser) as http://localhost/webapp/myapp#top > > instead of using the URL that generated the page. This causes the > browser > > to go back to the home page of the app rather than just scrolling to the > top > > of the page. > > > > Is there a simple solution? > > > > Richard > > > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by: OSDN - Tired of that same old > > cell phone? Get a new here for FREE! > > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > > _______________________________________________ > > Tapestry-developer mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/tapestry-developer > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer > > > > Protect yourself against identity theft with Equifax Credit Watch. Visit > http://www.creditalert.equifax.com. > > This message contains information from Equifax Inc. which may be > confidential and privileged. If you are not an intended recipient, please > refrain from any disclosure, copying, distribution or use of this > information and note that such actions are prohibited. If you have > received this transmission in error, please notify by e-mail > [EMAIL PROTECTED] > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer > ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
