Yes, we don't have to start from scratch. But follow me, the timeout
variables should be different in these 2 modes... I still remember the
thread in this group referring to "an irritating loss of code" due to
timeouts...
There is no real need for authentication in Development mode (Just
like I don't authenticate myself in Emacs and Eclipse)... There is no
need for GUI in the production mode....
And I don't think this requires extensive unit tests, as long as we
work on this wisely.
e.g. If I remove the presentation banner and GUI it's reasonable to
assume that my applications won't behave any differently as long as
the server is ON in the same port.
On Mar 12, 1:52 am, AchipA <attila.cs...@gmail.com> wrote:
> We kind of already have this, but perhaps not as clearly defined or
> with a 'master switch' for it. You can change logging levels via the -
> D switch. We have 'compile app'. The autoreload is just a model
> setting away:
>
> if DEBUG: reload('funky.module')
>
> Cache stuff is a tad more tricky, especially with the slightly
> unexpected timing logic web2py has, but I guess, there too you could
> use a model setting
>
> cachetime = lambda x: if DEBUG: return 0 else: return x
>
> cache.ram('key', lambda: stuff, cachetime(60))
>
> On Mar 11, 8:10 pm, blackthorne <francisco....@gmail.com> wrote:
>
> > hi
>
> > As my experience with web2py grows I find an increased need to make it
> > work in 2 main environments/behaviors.
>
> > The first mode would be "development" and it should run with smaller
> > buffers, extra debug features/output, auto-refresh for files like
> > routes.py so that you can edit routes on-the-fly, no caching
> > mechanisms that can trick the programmers and it could even be a
> > testing mode for new web2py features.
> > Then there would be "production" mode, meant to be simple, stable and
> > as fast as possible.
>
> > Thinking about it, doesn't make sense that such different usages run
> > the same way.
>
> > This idea doesn't break the convention over configuration philosophy
> > used in web2py.
>
> > Thanks
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
