On 11 October 2011 16:06, Christopher Van Kirk <christopher.vank...@gmail.com> wrote: > Isn't the point of cookies that all this sort of work is done for you? If > not, then perhaps you should consider storing (and accessing) the data in an > alternative way.
That is true... a web browser has to confirm to cookie contract, whereby it has a global cookie storage and attaches cookie to each request to the domain that cookie originated from. In Shruthi's case it is his application that has to fulfil this contract, in case he is using web view. As Mark suggested, retrieve and save to a file or a DB all cookies from a session upon exit and revert the process upon re-entry to the application. You could integrate it even more, by implementing your own CookieStore interface, that automatically uses storage or DB behind the scenes. Have a look at the following point: http://hc.apache.org/httpcomponents-client-ga/tutorial/html/statemgmt.html#d4e816 -- Daniel Drozdzewski -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
