The way the default code works, when the browser is closed the cookie no
longer works. Our system will delete cookies stored on the backend every
30 minutes, so a cookie will have to be resubmitted (recreated) at that
time as well.
At least, that's how I understand it works... someone more familiar with
cookies may say otherwise.
Charles Daminato
TUCOWS Product Manager (ccTLDs)
[EMAIL PROTECTED]
On Tue, 26 Dec 2000, Paul Rony wrote:
> I'm developing a sessionless environment, so how do you recommend that I
> delete the cookie if I don't have a timeout event?
>
> Paul Rony
> Merchantware
>
> -----Original Message-----
> From: Charles Daminato [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, December 26, 2000 10:52 AM
> To: Juha-Matti Tapio
> Cc: [EMAIL PROTECTED]
> Subject: Re: OpenSRS Client Protocol
>
>
> The cookie is used to maintain authentication between the client browser
> and our system. It's session based, so you can close the connection to
> the server, as long as you maintain the cookie for as long as the end user
> is logged in to manage their domain name.
>
> Charles Daminato
> TUCOWS Product Manager (ccTLDs)
> [EMAIL PROTECTED]
>
> On Tue, 26 Dec 2000, Juha-Matti Tapio wrote:
>
> > I'm writing a client that uses the Perl library and there are a few things
> > that I'm wondering.
> >
> > What is the purpose of the cookie in get domain and modify domain?
> >
> > Is the cookie only valid within one connection or can I close the
> connection
> > for a while before using the cookie?
> >
>
