Re: [mp2]"opaque string-content tables"

[prev] [thread] [next] [Date index for 2005/02/15]

On Tue, 15 Feb 2005, Stas Bekman wrote:

> Date: Tue, 15 Feb 2005 18:12:26 -0500
> From: Stas Bekman <stas@xxxxxx.xxx>
> To: Jie Gao <J.Gao@xxx.xxxx.xxx.xx>
> Cc: modperl@xxxx.xxxxxx.xxx
> Subject: Re: [mp2]"opaque string-content tables"
>
> Jie Gao wrote:
>
> >>>>What does it mean by "opaque"?
> >>
> >>
> >>
> >>On the C level that means: you can put in strings and whatever you put in
> >>your get out.
> >>
> >>On the Perl level that means that we convert any scalars into strings and
> >>store that. Any special information that was in the perl scalar is not
> >>stored. So for example if a scalar was marked as utf8, that flag is lost.
> >
> >
> > Thanks for the explanation.
>
> I've committed it.
>
> >>That explanation should probably live here:
> >>http://perl.apache.org/docs/2.0/api/APR/Table.html#Description
> >>
> >>if the way I've put it is clear, I'll add it there.
> >>
> >>
> >>>Also a related question about APR::Table:
> >>>
> >>>Does a table object contain all the name/value pairs parsed from the
> >>>request line (with arguments/query strings) and from the body of the
> >>>request (like from POST), in a situation of a POST form that has a
> >>>query string at the end of the URL?
> >>>
> >>>I know the CGI module does it well, but I do not want to use that
> >>>module for what I am doing at this time.
> >>
> >>I'm not sure I understand what you are talking about, Jie. Are we talking
> >>about something like $r->headers_in table? In which case it doesn't have
> >>any query string data, other than the unparsed one, which you should
> >>get/set via $r->args anyway. If not, please explain.
> >
> >
> > Thanks, Stas. I am now parsing both the request body and the $r->args now.
>
> When you will want a performance boost, you will want to switch to
> libapreq2 (Apache::Request).

Where is it?

Regards,


Jie