From: p dont think <pdontthink@an...> - 2002-11-30 09:49:30
> > Correct. If you don't have access to your mail
> > server, that is your
> > only option.
> Hmm, I wonder about the frequency of these cookies,
> if this is an autosave function. I can't get ANYTHING
> done when I get in this loop. I have to kill
> netscape, don't even have time to hit a cancel or back
> button. It's one cookie after the other in rapid
> succession, even over a 28.8 modem line. Maybe I
where once you've downloaded the compose screen, it sets the cookie
values locally, on your computer, completely independent of the server.
> could suggest to the admin that he adjust the
> frequency. I wouldn't mind dealing with this little
> cycle if it only happened every couple of minutes.
For one, why do you have your browser set like that? Cookies are a way
of life on the 'net nowadays, and a fact of life that most people just
accept. I understand the desire to control that kind of thing, and keep
some of those useless marketing oriented cookies off my machine, but it
just isn't worth my time - I've got bigger battles to fight. Second,
the timing of the autosave is frequent so that if you cancel a message
accidentally, the chances of losing something will be small. Most any
computer has enough extra CPU cycles wherein that does not affect
anything... every couple of minutes would defeat the purpose of the
The only thing would be for someone to expand the plugin so that the
value can be set by the end user (or turned off entirely)... I could do
that, although it's not my top priority currently...
> Do I know what I am talking about ? Is each of these
> six-cookie cycles a single autosave or does it take a
> number of cycles to save the whole?
> Thanks again. I wonder if this is of interest to
> anyone else on the list. Maybe I should do a little
> synopsis. Anyways, thx.
> > > -----Original Message-----
> > > From: Fabien Lamour [mailto:ghcbc@...]
> > > Sent: Friday, November 29, 2002 7:32 PM
> > > To: p dont think
> > > Subject: RE: [SM-USERS] endless cookie loop in
> > compose
> > >
> > >
> > > --- p dont think <pdontthink@...>
> > wrote:
> > > > This is normal. It is the quicksave plugin
> > doing
> > > > auto-saves of your
> > > > current compose session into a cookie. That's
> > how
> > > > it can restore it
> > > > later... if you don't want those warnings, turn
> > down
> > > > your browser
> > > > sensitivity or disable the Quicksave plugin.
> > > >
> > >
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.