Massimo, I believe Alec already has one he linked to: Keep an eye on this issue: http://code.google.com/p/web2py/issues/detail?id=872 so I'm assuming you don't need another one for essentially the same feature request.
:) On Monday, July 16, 2012 4:41:11 PM UTC-4, Massimo Di Pierro wrote: > > Please open a ticket. > > On Monday, 16 July 2012 13:09:29 UTC-5, rdodev wrote: >> >> Massimo, >> >> As Alec mentioned above, if not RESTful, OAuth and jsonrpc/jsonp would >> work as well. So if this is the preferred approach to non-browser/mobile >> authentication I could definitely work with that. >> >> Thanks. >> >> On Monday, July 16, 2012 1:59:30 PM UTC-4, Massimo Di Pierro wrote: >>> >>> Can you descrive in some details the API's you would like to have? >>> If there is agreement it would not much to add them. >>> >>> >>> On Monday, 16 July 2012 10:18:55 UTC-5, rdodev wrote: >>>> >>>> I'm developing a web2py app that will be used as the back-end for a >>>> mobile app. The mobile app will be making API calls to the service for >>>> anything ranging from login/authentication to CRUD operations. The auth >>>> model that comes baked into web2py would suffice, except that it's not >>>> RESTful and it's mostly geared to work with a web browser (sessions, >>>> cookies, etc.). Is there a way to set the auth module to behave RESTfully? >>>> >>>> Another issue is that some of the mobile clients might be running on a >>>> webView (phoneGap) and thus issuing requests to out back end would result >>>> in a same-origin policy denial. Is there a way to setup CORS in web2py (or >>>> should we set that up through apache/wsgi instead?) >>>> >>>> Thanks. >>>> >>> --
