Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much
 
PerlMonks  

Re^4: Plack and apache child init phase (PlackChildInitHandler)

by ysth (Canon)
on May 01, 2014 at 08:26 UTC ( [id://1084585]=note: print w/replies, xml ) Need Help??


in reply to Re^3: Plack and apache child init phase (PlackChildInitHandler)
in thread Plack and apache child init phase

Thanks, I had read the Plack::Handler::Apache2 doc but not the others.

I will give this a try, but...it's not clear to me how it is doing anything at child init time, not compile time.

--
A math joke: r = | |csc(θ)|+|sec(θ)| |-| |csc(θ)|-|sec(θ)| |
  • Comment on Re^4: Plack and apache child init phase (PlackChildInitHandler)

Replies are listed 'Best First'.
Re^5: Plack and apache child init phase
by Anonymous Monk on May 01, 2014 at 09:47 UTC

    I will give this a try, but...it's not clear to me how it is doing anything at child init time, not compile time.

    now you've confused me :) some more

    At what time, other than child init time, would any plackish webserver create an app object of your app and then wait for incoming requests?

    That is pretty much "child init time" in terms of PSGI ...

    So the app object is created, builder runs the "enable" callback, and then the webserver waits for requests to give to app

    Oh yeah, I see , it is no different than just doing it in the constructor :) except maybe slightly semantically different (if its not part of the app, then do nothing middleware seems appropriate)

    I think child_init_time is about knowing too much about the webserver

    PSGI is about apps, ::Middleware is about wrapping apps (daisy chain), and Plack::Handler is about connecting PSGI apps to webservers (hey random webserver run this app_

    I just can't see where child_init_time belongs as a PSGI/Plack concept ...

      At what time, other than child init time, would any plackish webserver create an app object of your app and then wait for incoming requests?

      Well, normally I want compilation to happen as early as possible; in a preforking server, this is at startup. child init is after that, whenever a new child is forked, but before actually waiting for incoming requests.

      --
      A math joke: r = | |csc(θ)|+|sec(θ)| |-| |csc(θ)|-|sec(θ)| |

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://1084585]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others chilling in the Monastery: (4)
As of 2024-03-29 15:51 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found