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=42&product=23 or /incident/search?manager=42&product=23 Marius On Mon, Sep 26, 2011 at 7:07 PM, will trillich <will.trill...@serensoft.com> wrote: > 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 Actions" got me to thinking it may be > feasible... For example: > /incident/my/loc/37/closed/20110401-20110430 > /incident/team/22/manager/138/product/417 > /incident/manager/138/product/417 > Advantages: easy for the browser to bookmark and return to, later > Disadvantages: chaining? other? > If using the URL is a bad way to 'store' the search parameters, what's a > good way to cache them in the session info? > -- > "The very nucleus of Character: to do what you know you should do, when you > don't want to do it." Stephen Covey > > _______________________________________________ > List: Catalyst@lists.scsys.co.uk > Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst > Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ > Dev site: http://dev.catalyst.perl.org/ > > _______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/