On Thu, 28 Aug 2014 16:27:20 -0300, George Christman
<gchrist...@cardaddy.com> wrote:
Your absolutely correct, context URLs are much better for SEO than
request
parameters. I tend to use both at the same time, example
domain/category?make=ford, category being the context. I think what
you've
done is a cool idea, however with the amount of filters that we will end
up
having, it would get real messy when they are mostly all null. It would
end
up looking something like this.
domain.com/category/make/$N/$N/$N/$N/$N/$N/$N/$N/$N/$N/brown
You can avoid the $N by providing your own
org.apache.tapestry5.services.URLEncoder.
Some of the newer stuff I have planned will look something like this.
http://www.cardaddy.com/used-cars/2011-toyota-corolla-le-albany-ny-12205-4978?_rd=50&color=brown
You could also map the other parameters into a single string and pass it
as an activation context value. In this case, you'd need to do the string
<-> parameters map yourself.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
