Re: Namespace confusion

[Joe Schaefer]

jonathan vanasco <[EMAIL PROTECTED]> writes:

>   Should I be using the APR::Request / APR::Request::Cookie
> methods instead of Apache2 ?

Yes; with one caviat.  The freeze/thaw methods for
APR::Request::Cookie are noops, but the freeze/thaw
methods Apache2::Cookie are compatible with CGI.pm
and the old 1.x Apache::Cookie API.  So I'd personally
only use Apache2::Cookie if I needed those freeze/thaw
methods and didn't want to roll my own versions.

>   If so, why no APR::Request::Upload?

Don't need it, since APR::Request::Param includes
those APIs.


-- 
Joe Schaefer

Namespace confusion

[jonathan vanasco]

Installed:

Apache2::Request
Apache2::Cookie
Apache2::Upload

APR::Request
APR::Request::Cookie

In a recent posting:
"...the APR::* classes will be the
ones we recommend nowadays.  We debated whether to chuck the Apache2::*
classes entirely, but we left them in for back-compat reasons."

Now:
I'm at a loss

	Should I be using the APR::Request / APR::Request::Cookie methods 
instead of Apache2 ?

If so, why no APR::Request::Upload?