I am a bit lost. What are you trying to achieve?
On Sep 22, 2:56 am, Niphlod <niph...@gmail.com> wrote: > I'm sorry to keep up the thread...do you think that replacing all the > "redirects" in the auth module, or overloading all decorators to raise > HTTP(404) instead of redirecting can be feasable/will work? > > Right now web2py is packed with a really nice set of features(oauth, > openid, rss, csv, rtf, amf, soap, pdf generation, maybe xslx > export(just read hehe), ), and the only "part" that is not keeping up > the pace is creating apis and services... > I don't use django-piston but it seems to be really widely accepted... > regarding its features: > > - Ties into Django's internal mechanisms (who cares) > - Supports OAuth out of the box (as well as Basic/Digest or custom > auth.) (web2py has it, but auth module is really tied into the "web" > world and not for the "services" one) > - Doesn't require tying to models, allowing arbitrary resources. > (web2py too) > - Speaks JSON, YAML, Python Pickle & XML (and HATEOAS.) (maybe hateoas > is missing, but, again, who cares ?) > - Ships with a convenient reusable library in Python (mmhmh...) > - Respects and encourages proper use of HTTP (status codes, ...) (this > can be implemented lately) > - Has built in (optional) form validation (via Django), throttling, > etc. (I think that web2py has yet goodies to do it) > - Supports streaming, with a small memory footprint. (web2py has it) > - Stays out of your way. (but requires django....^_^) > > On 5 Ago, 21:56, Niphlod <niph...@gmail.com> wrote: > > > perfectly working, thanks again. > >
