Thanks!
Am 18.03.2011 18:10, schrieb Jeff Trawick:
What's the big picture here? Is it something like
IF YOU USE THE UGLY LEGACY HTTPD 1.3/2.0 MODEL:
* dudette, your code still works (but shame on you for not using the
2.2 provider framework)
that would be nice - but that worked only with 2.2, but
On Fri, Mar 18, 2011 at 1:10 PM, Jeff Trawick traw...@gmail.com wrote:
after gathering pages of scribbles from comparing
2.2.x/modules-2.3.x/modules and 2.2.x/include-2.3.x/include for
API changes and trying to describe as many as I could, I'm left with a
list of things to research further:
On Friday 18 March 2011, Jeff Trawick wrote:
after gathering pages of scribbles from comparing
2.2.x/modules-2.3.x/modules and 2.2.x/include-2.3.x/include for
API changes and trying to describe as many as I could, I'm left
with a list of things to research further:
I'll try to provide some
Am 22.03.2011 15:52, schrieb Jeff Trawick:
On Fri, Mar 18, 2011 at 1:10 PM, Jeff Trawicktraw...@gmail.com wrote:
after gathering pages of scribbles from comparing
2.2.x/modules-2.3.x/modules and 2.2.x/include-2.3.x/include for
API changes and trying to describe as many as I could, I'm left
after gathering pages of scribbles from comparing
2.2.x/modules-2.3.x/modules and 2.2.x/include-2.3.x/include for
API changes and trying to describe as many as I could, I'm left with a
list of things to research further:
check_user_id-check_authn
access_checker-check_access
