Stuart -- This sounds very intriguing.
Can you share some code or pseudocode? That would be very instructive.
Thanks!
On Wed, Jun 2, 2010 at 1:23 PM, Stuart Watt sw...@infobal.com wrote:
Actually, I'll elaborate our more detailed solution.
1. We don't actually use POST requests for
On 2 June 2010 18:56, w...@serensoft.com w...@serensoft.com wrote:
Short version:
Using [% c.req.uri_with({ page = pager.next_page }) %] is fine for a simple
single-field search (where the form uses GET instead of POST)... but how do
we PAGE through (and/or cache) a multi-field form search
Bill -- We're running Catalyst::Runtime 5.80022 but uri_with comes via
Catalyst::Request which doesn't appear to have a $VERSION specified. This is
on Debian 5.0.4 (stable) but we've had to use CPAN to get more modern
versions of many of the Debian libraries to get around the uses NEXT which
is
On 4 June 2010 17:26, w...@serensoft.com w...@serensoft.com wrote:
Bill -- We're running Catalyst::Runtime 5.80022 but uri_with comes via
Catalyst::Request which doesn't appear to have a $VERSION specified. This is
on Debian 5.0.4 (stable) but we've had to use CPAN to get more modern
versions
i forgot
form method=POST
2010/6/3 Oleg Pronin syber@gmail.com:
form id=myform
input type=hidden name=... value=.../
... any number of params
input type=hidden name=page value=[%page%]/
...
a href=# onclick=$('#myform input[name=page]').val(2);
$('#myform').submit()
Page 2
form id=myform
input type=hidden name=... value=.../
... any number of params
input type=hidden name=page value=[%page%]/
...
a href=# onclick=$('#myform input[name=page]').val(2);
$('#myform').submit()
Page 2
/a
/form
2010/6/2 w...@serensoft.com w...@serensoft.com:
Short
Short version:
Using [% c.req.uri_with({ page = pager.next_page }) %] is fine for a simple
single-field search (where the form uses GET instead of POST)... but how do
we PAGE through (and/or cache) a multi-field form search that uses POST?
Long version:
This is probably already a posted recipe
We do a redirect code 303 from the POST request handler to a GET handler
and page through it instead. This appears to be the HTTP 1.1 norm, and
anything else is risky, as POST is expected to change stuff in the
database. Paging through a POST result will (might) cause multiple
changes. This
Actually, I'll elaborate our more detailed solution.
1. We don't actually use POST requests for search, but our GET requests
have many fields and strange Dojo magic
2. We serialize the query with its many fields, using a bit of
compression on the URI query string, and base 64 encoding, into a
