The cookies was an easy and strait forward implementation. Adding response.cookies['myCookie'] = 'myData' in the web2py default controller (that the user will visit once logged in) and using the CookieManager Class on the app side provided a simple solution. Thanks, Yuval
On Jan 16, 8:10 pm, Bruno Rocha <[email protected]> wrote: > You can redirect the user after login to a new url and post user ID as args > or vars, so in client side I think you can take it from location. Or you > can set a <input hidden> with the value and read it with jquery, or the > cookie. > > > > > > > > > > On Tue, Jan 17, 2012 at 2:07 AM, Yuval <[email protected]> wrote: > > This is on the server side, I looked for the better way to get it over > > from the server to the mobile application/ client side. > > I will just set the user id in a cookie and I will pick up from the > > cookie on the mobile application side. > > > Thanks > > Yuval > > > On Jan 16, 4:50 pm, Yuval <[email protected]> wrote: > > > I need the web2py user id on an android mobile application. > > > > The user will use a web page (WebView) to perform the login (or to > > > register). > > > > Once logged in, what is the best suggested way to pass back the user > > > id to the container application (browser)? > > > > Thanks, > > > Yuval > > -- > > Bruno Rocha > [http://rochacbruno.com.br]
