you could always save session ids on local sqlite database. never tried but should work, also it should be more secure than cookies... but surely slower.
On Jan 20, 1:45 pm, David Ethell <[email protected]> wrote: > In our application we just generated a unique session id on the > backend and saved that in a cookie in the browser. So when you open > the app again it sends that session id and the backend looks it up in > the valid sessions to find the user. > > However, it seems that the lifetime of cookies is not working > correctly for us as sometimes it remembers the login and other times > it does not. So I'm curious as well to see how people are doing this. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en -~----------~----~----~----~------~----~------~--~---
