What I meant was, "writing" documents are a context-switch from coding, so if there are detailed design notes in the code, let me know. Thanks.
On Tuesday, September 4, 2012 9:40:50 AM UTC-7, ozwyzard wrote: > > Thank you. Is there some document that would talk a few points on > context, threads, (locking issues if any), etc. Or does one have to read > the dispatcher code? Sometimes documents are a context-switch for the > brain. If there are any detailed notes in the code or README_DESIGN.txt in > a separate file, let me know. I have the pylons book, but do not recollect > it going into such detail. Thanks again. Congratulations on TG 2.2! > > On Tuesday, September 4, 2012 1:13:02 AM UTC-7, Alessandro Molina wrote: >> >> On Tue, Sep 4, 2012 at 4:28 AM, ozwyzard <[email protected]> wrote: >> > Thanks for confirming that it would lead to race conditions. Agree >> that one >> > can store request context variables in request or tmpl_context. Thank >> you! >> > >> >> It actually depends on the TG version as some reuse the controller >> instance for multiple requests, >> for that reason relying on the ability of storing controller >> properties is not suggested. >> > -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To view this discussion on the web visit https://groups.google.com/d/msg/turbogears/-/7meMh5VMWG4J. 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.
