We are not going to have to go into that much detail for our apps thought are we.
Will we be able to take advantage of the multi-threading by simply creating multiple request handlers. I imagined I would be changing a few lines of code in my main function an that's about it. On Jun 29, 9:43 pm, Joshua Smith <joshuaesm...@charter.net> wrote: > I would assume they are the same as the basic principles of thread safety in > any language: > > - Don't rely on global state, because multiple of your functions might be > running simultaneously > > This usually isn't very hard to achieve - just pass parameters instead of > modifying globals. The places where it can get tricky are where you really > *want* to use global state, such as for an in-memory cache. Usually the > language provides some primitives to ensure that only one thread at a time is > updating the cache. It appears that python gives you thread-safety for a lot > of cases: > > http://effbot.org/zone/thread-synchronization.htm > > On Jun 29, 2011, at 1:20 AM, Greg wrote: > > > > > > > > > Hi - > > > Could anyone familiar with threads explain the basic principals of > > python thread-safety? > > > Cheers! > > Greg. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine" group. > > To post to this group, send email to google-appengine@googlegroups.com. > > To unsubscribe from this group, send email to > > google-appengine+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
