Remy,
Thanks for the response. The reason for my interest in access from the
client side is whether it could be used access some state information
created by the server.
In the interim I used some hidden Tlabels to accomplish that task. If I
needed access to something more structured I thought I would just save it to
a local xml file.
By the way under what circumstances would I use the TIdCookieManager?
David
"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:4411f2a2$1@newsgroups.borland.com...
>
> "David Fealkoff" <fealkoff@iatinc.net> wrote in message
> news:4410d9bd$1@newsgroups.borland.com...
>
>> I don't know what role, if any, cookies play in that.
>
> Everything. A session uses a cookie to identify itself to the client.
> Every request made by a client has to send back that cookie, or else the
> client's existing session cannot be found. The reason for using a cookie
> is
> for situations where the client disconnects from the server between each
> request, but makes multiple requests to the same server within the session
> timeout. That is very common for HTTP clients to do, especially if they
> are
> using HTTP v1.0 rather than v1.1.
>
>> I don't if cookies are being created on the client side
>
> Cookies are always created by the server. It is the client's
> responsibility
> to only keep track of them and then send them back later when appropriate.
> TIdHTTP and TIdCookieManager handle that automatically.
>
>> what information is contained in them
>
> The domain, and optionally the specific URL, that the cookie belongs to,
> when the cookie expires, and the data for the cookie.
>
>> and how to access the information on the client side.
>
> Why do you need to do that?
>
>> If I could get a brief explanation and/or some snippets or demo
>> source code that would handle the issues in item 3 that would be great.
>
> Everything you are asking for should be handled automatically. What
> EXACTLY
> are you having problems with, if any?
>
>
> Gambit
