I'm trying to seek out any bugs, but the only thing I've found so far is
that $r->pnotes('xml_string') never actually gets set. Nothing at all in
pnotes is set on the SubRequest object.

My life is currently one big time crunch, so because document('http://')
scheme still works I'm going to just use that for now. When my project is
complete and I can go back and start optimizing I'll continue the debug
process, and hopefully get some good info for you.

Thanks again!
Riley

----- Original Message -----
From: "Matt Sergeant" <[EMAIL PROTECTED]>
To: "Riley James" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, August 09, 2002 5:28 AM
Subject: Re: AxAdd*Processor and the axkit:// scheme


> On Fri, 9 Aug 2002, Riley James wrote:
>
> > I noticed mention of "AxAddDynamicProcessor" in the CONTRIB file of the
> > distribution, but can't find any information on what it is or does.
Could
> > someone enlighten me?
> >
> > Also, I was wondering if the axkit:// scheme issue initally expressed on
> > this list by  Chris Wenham works for anyone else. I have the same issue
that
> > Chris did, and I remember from posts on mod_perl that we are both
running
> > FreeBSD. I can see in my logs that the XSP page is processed, but it
fails
> > with "document empty". I tried to check out and install the latest from
CVS,
> > hoping to cure this, but apache start fails with those damn libiconv()
> > errors. I hate those. So I'm back to the 1.6 off of CPAN, which works
> > beautifully in every other way...
>
> I kinda need someone to debug this for me. I got a simple axkit:// demo
> working here, and so deemed it ready to ship. But like all new features
> it's bound to be flaky at first. So please can you put some
> AxKit::Debug()s in AxKit.pm where it does the axkit:// stuff, and see if
> it's getting the output?
>
> --
> <!-- Matt -->
> <:->Get a smart net</:->
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to