I have a Catalyst application that is only handling part of the URL space of an existing application. The existing application saves some state information in the query string of every link. Therefore, the query string must be maintained when linking from the Catalyst part of the app back to the non-Catalyst part of the application.
There's always a session available to save the parameters while in the Catalyst app. It's a know list of parameters that must be preserved. What do you recommend? Override uri_for() and make sure that every URI generated includes the query paramters, even links within the Catalyst part that will not use the parameters? Or save the query parameters in the session at the start of the request and create a separate wrapper method around uri_for() for creating URLs back to the non-Catalyst part of the application that adds the query parameters back in? -- Bill Moseley [email protected]
_______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
