Thank you all for your explanations, this really clarifies things a lot, appreciated. I guess I'll apply the "patch" soon then.
François On 1 avr, 16:00, "Diez B. Roggisch" <[email protected]> wrote: > On Apr 1, 2011, at 2:58 PM, F. Poirotte wrote: > > > Hi, > > > Thanks for the quick reply. > > By any chance, do you know why this is necessary? > > That snippet looks like black magic to me and I'd rather have some > > strong technical background on this issue before I change the code on > > our production servers. > > > I remember seeing a note somewhere on turbogears website saying that > > you may need to "preload" the application in case you use load- > > balancing services and such. It that somehow related to the issue at > > hand? (we don't use any load-balancing on our servers, so I never gave > > any attention to that warning) > > The snippet will in fact force the mod_wsgi-process to pre-load the full > application controller hierarchy. As a result, all the tosca-widgets should > be instantiated, and their resources registered in the resource-middleware. > > The reason this needs to be done is because usually, you run mod_wsgi with > several processes. Lets name these P1-P10. > > Now if a request hits a freshly started apache (without the "magic lines"), > it hits P1. That initial request is directed at a controller action, so the > full TG2 app with it's controller hierarchy is bootstrapped. All is nice and > easy. > > The resulting HTML now contains several references to static resources from > TW. So the browser will - in parallel - request these. Because P1 is just > finished, it probably won't even getting any of these requests. Instead, the > are distributed amongst P2-P10. > > And these processes are not bootstrapped yet. So, TW doesn't know about any > resources when asked, and the result is a 404 or 500. > > And for that reason, the "magic snippet" is there. > > It is unfortunate, but I don't see any other way. You could try & have some > sort of finalizing method-call into the Pylons/TG2-stack that essentially > does the same, but the underlying technology won't be changeable. > > Diez -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
