I understand unrestricted access to cookie jars can be bad for your health, but it's annoying that you can't have two Dillos using cookies at the same time. I usually have a Dillo running permanently, and when I get a URL in my mail, I can click on it to open another Dillo (quickly!) -- but that Dillo can't use cookies, which is frequently (e.g. in bugzilla) necessary. Could we do a write-lock on it? -Lars -- Lars Clausen (http://shasta.cs.uiuc.edu/~lrclause)| Hårdgrim of Numenor "I do not agree with a word that you say, but I |---------------------------- will defend to the death your right to say it." | Where are we going, and --Evelyn Beatrice Hall paraphrasing Voltaire | what's with the handbasket?
Hi, Lars Clausen <lrclause@cs.uiuc.edu> writes:
I understand unrestricted access to cookie jars can be bad for your health, but it's annoying that you can't have two Dillos using cookies at the same time. I usually have a Dillo running permanently, and when I get a URL in my mail, I can click on it to open another Dillo (quickly!) -- but that Dillo can't use cookies, which is frequently (e.g. in bugzilla) necessary. Could we do a write-lock on it?
That is something I would appreciate as well. I have been running with this ugly patch that disables locking for atleast 6-7 months without a problem: --- src/cookies.c.orig Sun Jan 12 01:25:20 2003 +++ src/cookies.c Mon Feb 24 09:43:37 2003 @@ -31,7 +31,6 @@ #include "list.h" #include "cookies.h" -#define DEBUG_LEVEL 8 #include "debug.h" /* The maximum length of a line in the cookie file */ @@ -140,7 +139,7 @@ void a_Cookies_init() char line[LINE_MAXLEN]; /* Default setting */ - disabled = TRUE; + disabled = FALSE; /* Read and parse the cookie control file (cookiesrc) */ if (Cookie_control_init() != 0) { @@ -158,6 +157,7 @@ void a_Cookies_init() return; } +#if 0 /* Try to get a lock from the file descriptor */ disabled = (lockf(fileno(file_stream), F_TLOCK, 0) == -1); if (disabled) { @@ -166,7 +166,7 @@ void a_Cookies_init() fclose(file_stream); return; } - +#endif DEBUG_MSG(10, "Enabling cookies as from cookiesrc...\n"); cookies = g_hash_table_new(g_str_hash, g_str_equal);
Lars,
I understand unrestricted access to cookie jars can be bad for your health, but it's annoying that you can't have two Dillos using cookies at the same time. I usually have a Dillo running permanently, and when I get a URL in my mail, I can click on it to open another Dillo (quickly!) -- but that Dillo can't use cookies, which is frequently (e.g. in bugzilla) necessary. Could we do a write-lock on it?
Actually, we plan (with Jörgen) to make of cookies a dpi server. Cheers Jorge.-
On Fri, 25 Apr 2003, Jorge Arellano Cid wrote:
Lars,
I understand unrestricted access to cookie jars can be bad for your health, but it's annoying that you can't have two Dillos using cookies at the same time. I usually have a Dillo running permanently, and when I get a URL in my mail, I can click on it to open another Dillo (quickly!) -- but that Dillo can't use cookies, which is frequently (e.g. in bugzilla) necessary. Could we do a write-lock on it?
Actually, we plan (with Jörgen) to make of cookies a dpi server.
Now *that* would be a good use of the dpi server. Shouldn't be horribly hard, and then the plugin can have a nice admin interface if it wants to. -Lars is still miffed about the bookmarks menu. -- Lars Clausen (http://shasta.cs.uiuc.edu/~lrclause)| Hårdgrim of Numenor "I do not agree with a word that you say, but I |---------------------------- will defend to the death your right to say it." | Where are we going, and --Evelyn Beatrice Hall paraphrasing Voltaire | what's with the handbasket?
participants (3)
-
Gabriel Kihlman -
Jorge Arellano Cid -
Lars Clausen