apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <wr...@rowe-clan.net>
Subject Re: apr_uri_string_encode/decode
Date Wed, 02 Aug 2006 18:22:58 GMT
Justin Erenkrantz wrote:
> On 8/2/06, david reid <david@jetnet.co.uk> wrote:
>> Of course it does raise the question about where should these live? If
>> we consider them to be "strings" function then they probably belong
>> inside apr's strings funcs, but if they are "uri" functions then this is
>> the correct place. Thoughts?
> 
> If it's quoting based on the rules in the URL RFC, then apr_uri_ makes
> the most sense.  Now, the function you posted is called
> apr_uri_query_string_decode, but I thought this was for general URI
> encoding?  Or, is this only for query strings?  -- justin

That raises a productive suggestion; apr_uri_http_ for http-protocol specific
parsing, apr_uri_ldap_ for ldap-protocol specific parsing etc ad nausem.



Mime
View raw message