On Mon, Apr 13, 2009 at 2:34 AM, mdipierro <[email protected]> wrote: > This is not an easy one. The problem is that the routes code is > outside any app. Currently if there is a bug in routes, web2py does > not start. If you allow changes at runtime: 1) you make web2py slower > because changes have to be monitored; 2) what happens if there is a > bug in routes?
Yes, I know about that problems. But in a shared host, what I can do to solve this? -- Álvaro Justen Peta5 - Telecomunicações e Software Livre 21 3021-6001 / 9898-0141 http://www.peta5.com.br/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
