caudium-devel AT caudium.net
Caudium Developer mailing list.

Re: PATH_INFO (was: Re: [caudium-devel] Odd problem with caudium)


chronological Thread 
  • From: Bertrand LUPART <bertrand.lupart AT linkeo.com>
  • To: caudium-devel AT caudium.net
  • Subject: Re: PATH_INFO (was: Re: [caudium-devel] Odd problem with caudium)
  • Date: Tue, 21 Feb 2006 14:31:32 +0100

The filesystem module is MODULE_LOCATION.

As Martin said and according to the flow chart on the Caudium website
(http://caudium.net/server/docs/modules.rxml), MODULE_FIRST should be
called (in random order) before MODULE_LOCATION (they are).
Yeah, and within the class (like Martin pointed out) they are kept in a
mapping, which means they're effectively in random order - that is unless
you move any of them to a higher priority (within the priority class they're
random as well). I think we should do something about the randomization -
the behavior should be predictable, be it even alphabetic.

Why not. I always thought having modules of the same type called in random order bring on side effects, but i never had any problem with that for now.

I did not dig further yet (used a MODULE_PRECACHE). That's maybe
related to your problem.
It turned out to be the PATH_INFO module that started to block
gsessions all
of the sudden... Very frustrating.

You ran into the very same problem than me.

Loaded the gsession module, and according to the CIF path resolver,
gsession is called when my own MODULE_FIRST is called, too.
For me it _always_ got called for implicit urls (like site.com/ stuff/) but
explicit urls (site.com/stuff/index.html) weren't ever passed to gsession.
Shouldn't we just make the whole stuff into a chain of filters instead?

Unless a MODULE_FIRST returns something different from 0, that's like a chain of filters, right?

Unload PATH_INFO and everything is fine.
Well, that's not fine at all because i'm planning to use PATH_INFO in
the very near future :)

After having a quick look at pathinfo.pike, it seems that first_try()
returns 1 when a file exists.
My guess is something is wrong here (but today is meeting day).

Look at this:

http://cvsweb.caudiumforge.net/cgi-bin/cvsweb.cgi/caudium/server/ modules/misc/pathinfo.pike.diff?r1=1.11;r2=1.12;cvsroot=caudium;f=h

What means "return 1" when used in last_resort() exactly? That's not listed here:
http://manuals.oav.net/programmer/responses/index.html

Does anyone extensively use the PATH_INFO module?
It's goal is to feed some data in the request id object and return. I can't see any case where it should return something else.

There are a lot of things that are wrong about 1.4+ alas :(

Bring them one at a time on this mailing list, i guess everyone will be happy to fix things :)

--
Bertrand LUPART
                       Linkeo.com | http://www.linkeo.com
                +33 1 72 71 71 84 | 17, rue de la Banque - F75002 Paris





Archive powered by MhonArc 2.6.10.

§