well, currently i have it so that page links are rendered as .html paths which the user see. when the system gets a request for a .html url it translates that into the /app? page syntax, but it doesnt do a redirect so the user never knows that it did that.
i'm also considering doing something similar with direct links so that all direct links will produce something like /admin/page.direct or something and then that will get mapped as it comes out as /direct/admin/page.html or something. then when the user requests it it gets translated back into the /app? syntax. urlrewritefilter is really great for this. tapestry never knows about the mapping and the user never knows about ugly urls. the built in solution for friendly urls was fine for a little bit but you can really do a lot more this way. On Thu, 2005-10-06 at 22:41 -0400, Kevin Menard wrote: > On Thu, 06 Oct 2005 17:28:33 -0400, Dan Adams <[EMAIL PROTECTED]> wrote: > > > well, i was using friendly urls before and mapping all .html to the > > tapestry servlet. So what I did instead is i got the urlrewritefilter > > and used it to rewrite all the urls i wanted to: > > > > /app?page=$1&service=page > > > > so to the user it looks the same as it did before. :) > > I haven't tried this, but it seemed like a popular option for T3 friendly > URLs. A lingering question I have though is won't the link renderer still > render ugly URLs that the user will be exposed to? > -- Dan Adams Software Engineer Interactive Factory --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
