Thanks for the reply Thiago, I have a question about this item:
>> Page Context >> Store the search criteria in the page context (by encoding it into a >> string representation?). It seems like a large number of sites store >> their search criteria into the pages URL in one manner or another, >> however this results in some rather long and ugly URLs > > IMHO, this isn't ugly, at least with a not large number of parameters. And > Tapestry's activation context is way prettier than normal parameters > (?a=1&b=2). The page context is exactly what I would choose in this > scenario. How would you set it up? If I have variable number of search criteria (the user can leave some criteria empty, also some searches I've seen let users add new criteria rows), wouldn't I need to have some sort of key value pair listing? Or would you simply map all values as though they had entered something? My search page will end up being fairly complex. In particular, could you show an example URL for the page you might generate (ie, the alternative representation to the "?a=1&b=2" example you have given? I assume you don't mean "pagename/1/2/" because then you can't deal with a variable argument list (you would have to encode every search parameter even if the user hasn't entered it right?). Maybe something like "pagename/a=1/b=2"? Thanks again, pete.pou...@gmail.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
