-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tim Esselens schrieb: > Tom Schindl wrote: > > >>Does this really make sense? You are printing the pointer of the pointer >>to the apache request object. > > > You're right, I've should have printed $r, which yields: > > Apache2::RequestRec=SCALAR(0x9d44644) [first n times] > Apache2::RequestRec=SCALAR(0x9d7e0a4) > (n begin the number of apache children) > > Am I correct in assuming that the Apache2::RequestRec object is now sitting > in 0x9d44644 or is that just the mem address of the scalar, which changes, > but is still pointing to the same RequestRec.
No. For every Request a ***NEW*** Request object is created! It's only the pointer to it is written to the same location (e.g. 0x9d44644) but maybe I'm not correct here. Where from do you know that the request is served from a different child at least the code you posted does show any about put about the child handling the request apache does not rotate the children used: - - 1. request => child 1 - - 2. request => child 2 - - 3. request => child 2 - - 4. request => child 4 You have to also print the $$ if your are running in prefork mpm, if you are running in a threaded mpm I have no idea how to distinguish between the different threads although there surely exists a thread ID or something like this. Tom -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC3kb7kVPeOFLgZFIRAuiUAJ9dl3zesEpV7aZMq0PsXSxtPXhV2wCcCYFd ELOY+/wk1eW2uD3B+lP9Ecg= =5+ty -----END PGP SIGNATURE-----
