fwd: Re: [Mono-devel-list] SimpleWorkerRequest patch for PATH_INFO

[eric lindvall]

is it only on that one aspx?

i've looked at the code again and i'm having trouble seeing how it could
impact anything:

-- From XSP:
        public abstract class MonoWorkerRequest : SimpleWorkerRequest
        {
                .
                .
                .
                public MonoWorkerRequest (IApplicationHost appHost)
                        : base (String.Empty, String.Empty, null)
                {

                        .
                        .
                        .
                }
                .
                .
                .
        }

-- From SimpleWorkerRequest:
        public class SimpleWorkerRequest : HttpWorkerRequest
        {
                .
                .
                .
                public SimpleWorkerRequest (string Page, string Query, TextWriter Output)
                {
                        _Page = Page;
                        .
                        .
                        .
                        ExtractPagePathInfo();
                }
                .
                .
                .
                private void ExtractPagePathInfo ()
                {
                        if (_Page == null || _Page == String.Empty)
                        {
                                return;
                        }
                        .
                        .
                        .
                }
        }

---------------

the code path that is taken in the SimpleWorkerRequest with the
MonoWorkerRequest is very short. the first check in ExtractPagePathInfo()
(as you can see) does no PATH_INFO parsing if _Page is null or empty
(which as you can see is what is passed in from MonoWorkerRequest).

is your xsp process pegging the cpu or just sitting there?

e.


On Wed, 25 Jun 2003, Gonzalo Paniagua Javier wrote:

> El mi? 25-06-2003 a las 19:04, eric lindvall escribió:
> > i also just realized it would be close to impossible for the PATH_INFO
> > patch to do something bad to XSP, because you are passing String.Empty to
> > the constructor of SimpleWorkerRequest (thus it doesn't have any
> > processing to do).
> 
> Well, the fact is that it hangs with the patch applied and it does not
> when i remove the patch :-/