Glenn,
I don't *want* to delete some of them! If I did, on certain sites where
I want to stay "the same person" I'd be a "different person" each time I
went to that URL [that's how I realized that the cookie.lst was being
eaten]. On another site, I need 3 different permanent cookies ... for
three different services offered by the site [actually, personalized
cartoons ... sometimes I like seeing my name appended to something that
brings a smile]. The Yahoo cookies I don't worry about *too* much,
although when I'm dealing with the webring they took over it can be a
great help to have the cookie ID me rather than have to start from
scratch at another page entirely.
I guess, since no one answered my questions, I'll just keep my backup
cookie file, and periodically update it if I find new sites where I want
the cookie to remain always the same [I lost my B&N cookie already,
darnit, and will have to get a new one for ordering on-line from my
primary parts supplier].
Thanks anyway ...
l.d.
====
On Sat, 10 Feb 2001 22:34:18 -0500, Glenn McCorkle wrote:
> On Fri, 09 Feb 2001 18:18:24 -0500, L.D. Best wrote:
>> Glenn,
>> I'll be saving your message, and seeing if I can use that setup. I take
>> it that the Caldera OpenDos utility "FIND" will work under other
>> DOSes?
> I can't say from personal experience.
> (never tried it with any DOS other than OpenDos) <g>
>> It is a start.
>> My new questions are:
>> 1. What management scheme does Arachne have for COOKIES.LST?
>> 2. It would seem to me that Arachne limits it to 256 lines, but *which*
>> lines? Does it add new lines at the top of the file or the bottom?
>> Or stick them in apparently at random like HISTORY.LST seems to
>> often do?
> Since I delete my cookie file every time I exit Arachne, I didn't know
> that it had a limit of 256.
>> 3. Considering how important cookies can now be on some sites, would it
>> be worth considering having a "permanent" cookie file that is copied
>> over to the working file each time we start Arachne?
> IMHO, Delete them.
> (you get a new one each time you visit the site again)
>> 4. And does anyone think that an APM for COOKIE.LST management could be
>> a good idea? [I'm backing off on having it built in, since the
>> hotlist manager never did get properly tuned, even though it had
>> some darn good ideas in it.]
> Same answer as for #3..... delete them.<g>
> --
> Glenn
> (your friendly neighborhood compu-nerd)
> http://arachne.cz/
> http://www.delorie.com/listserv/mime/
> http://freedos-32.sourceforge.net/
--
Join B'FOR - B'mothers For Open Records
<A HREF=" http://www.b-for.org "> B'FOR web site</A>
[Associate members of triad also welcome; membership confidential.]
Every member counts! We need numbers to produce valid statistics.
*******
A proud member of
<A HREF=" http://www.phenomenalwomen.com/ "> Phenomenal Women Of The Web</A>
-- Arachne V1.70;rev.3, NON-COMMERCIAL copy, http://arachne.cz/
