What do you think, should recommend using
if form.process().accepted:.... over if form.accepts(request,session):.... The only benefit is more compact notation. On Aug 16, 8:53 am, Anthony <[email protected]> wrote: > It still uses request.vars and session -- it just doesn't require you to > explicitly pass them as arguments (if you don't pass them, it uses > current.session and current.request.post_vars). > > Anthony > > > > > > > > On Tuesday, August 16, 2011 9:10:40 AM UTC-4, Richard wrote: > > Hello, > > > Since process() not require request.vars and session does it make things > > faster? > > > And if so, could it be percetible? > > > Thanks > > > Richard > > > On Mon, Aug 15, 2011 at 3:56 AM, Massimo Di Pierro > > <[email protected]>wrote: > > >> I agree with you that having three ways to do the same thing is not > >> good but: > > >> There are three reasons: > > >> 1) some people may want to validate without processing the form fully > >> (no insert). shortcut to accepts(...dbio=True) > >> 2) it allows to write onliners: form = SQLFORM(....).process() > >> 3) no longer need to pass request and session. > > >> see process() replacing accepts() and I see validate() as a way to > >> check if form validates without insertion. > > >> There are also some different defaults. If you do not pass a session > >> to accepts(...) you do not get CRSF protection. In process(...) you > >> must pass session=None explicitly to disable RSCF protection. > > >> We can talk more about these.... pros, cons, etc. > > >> These functions have been in web2py for a while. We just made them > >> work better. > > >> On Aug 15, 12:25 am, pbreit <[email protected]> wrote: > >> > I'm not totally clear on the gain here. Is it that flash messages get > >> > automatically set? Is this going to splinter implementations (ie some > >> will > >> > use .accepts, some will use .process, others will use .validate)? Is > >> that a > >> > good thing?
