Thanks Aaron. My next question:
Does it the request-to-class process _have_ to run continually, or can that itsself be called as required. I'm sure this isn't a good idea for production, but my development server won't allow long running processes. Thanks again, Pete. On Apr 17, 3:38 pm, "Aaron Swartz" <[EMAIL PROTECTED]> wrote: > The way web.py works by default is that when a request occurs it finds > the appropriate class, creates an instance of it, and calls the > appropriate method. > > The process that does this request-to-class mapping, however, can be > left running for long periods of time. For example, I have FastCGI > processes that have been running for months. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
