Catalystos:
I'm implementing a search screen and I'm wondering how impractical it would
be to have the URL be 'storage' for the parameters. Looking in the Cookbook
under DRY Controllers with Chained
Hi,
Consider using the query part of the URI to represent the search.
Browsers are very good at bookmarking these :)
If you have duplication, use the classic way of removing it, by
putting functionality in a third module or role.
Example
/incident/?manager=42product=23
or
On Mon, Sep 26, 2011 at 5:29 PM, Marius Olsthoorn olst...@gmail.com wrote:
Hi,
Consider using the query part of the URI to represent the search.
Browsers are very good at bookmarking these :)
What in the world is that supposed to mean? Are browsers *bad* at saving
bookmarks for other kinds
When the search-screen has a dozen or more fields (client requirements),
it's more likely that we use a POST instead of a GET. Bookmarking THAT ain't
so easy.
So instead of reiterating the original question, let me ask a related
question:
What's a good way to cache a search (so the user can
Kieren Diment
PhD Candidate
Health Informatics Research Lab,
Faculty of Informatics,
University of Wollongong
Tel: +61 4221 3952
On 27/09/2011, at 10:47 AM, Andrew Rodland wrote:
On Mon, Sep 26, 2011 at 5:29 PM, Marius Olsthoorn olst...@gmail.com wrote:
Hi,
Consider using the query
If you are using GET params for search, your search result itself becomes
identifiable as a distinct url. This kinda search result can be optimised in a
lot of ways. The best way IMHO is using a reverse proxy server to cache it
based on the url with a apt ttl.
-Shantanu
Sent from Samsung
