On 11 October 2011 16:41, Christopher Van Kirk
wrote:
> Hmm. Still sounds a bit dodgy. One wonders why this guy's use case
> necessitates him building a new browser, and whether a well placed intent
> would achieve his goal with a lot less effort.
Point taken... sometimes http client use could m
Hmm. Still sounds a bit dodgy. One wonders why this guy's use case
necessitates him building a new browser, and whether a well placed
intent would achieve his goal with a lot less effort.
On 10/11/2011 11:21 PM, Daniel Drozdzewski wrote:
On 11 October 2011 16:06, Christopher Van Kirk
wrote:
On 11 October 2011 16:06, Christopher Van Kirk
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,
wher
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.
On 10/11/2011 10:46 PM, Shruthi Varma wrote:
Hi All,
In my application, I get all the cookies from the post requests with
the
On Tue, Oct 11, 2011 at 10:46 AM, Shruthi Varma
wrote:
> I don't know how to save the cookies in an application.
>
> Because in the shared preferences, only primitive types (strings,
> integers, boolean values) can be stored.
Use an XML file. Or a JSON file. Or a file with one cookie per line.
Or
Hi All,
In my application, I get all the cookies from the post requests with
the HttClient.getCookieStore method.
I want to save these cookies so the next time the app is started, the
user don't have to log in.
I don't know how to save the cookies in an application.
Because in the shared prefer
6 matches
Mail list logo
