sussman_at_gmail.com wrote on 11/05/2008 11:08:15 AM:
> On Wed, Nov 5, 2008 at 11:01 AM, C. Michael Pilato <cmpilato_at_collab.net>
wrote:
>
> > I'll bet you a can of Starkist Solid White Albacore Tuna that you'll
get
>
> Wha? That's like betting a beer connoisseur a bottle of Miller Lite.
:-)
>
> > pressed into supporting the full peg-revision syntax if you open this
can of
> > worms. An easy way to lose the bet is to do nothing and wait for me
to
> > press you for it. ;-) An easy way to win the bet is to preclude the
> > pressing by adding the feature out of the box.
> >
> > path?[p=PEG&]r=REV (where P defaults to HEAD)
> >
>
> I'm fine with that. If you look at the revision I just committed
> (r34070), I have a simple TODO there:
>
> /* ### TODO: someday we should parse *all* query args into an
> apr_table_t, the way mod_form does. */
>
> Shockingly, you'd think that either apache or apr would provide an API
> to parse a long query string into a table, but I'm not seeing
> anything. Any volunteers?
I'm guessing you can borrow something from:
http://httpd.apache.org/apreq/docs/libapreq2/
Specifically, dig around in here:
http://httpd.apache.org/apreq/docs/libapreq2/files.html
At this point, I can't even volunteer the time to write
this email, let alone integrating the code...
Kevin R.
Received on 2008-11-05 18:41:20 CET