Hi Brian, Please keep this thread on dillo-dev. On Tue, Nov 09, 2004 at 08:12:50AM -0500, Brian Hechinger wrote:
On Mon, Nov 08, 2004 at 06:15:59PM -0300, Jorge Arellano Cid wrote:
Great! Now we have a man in charge of it.
i would be honored.
str = a_Prefs_get("font_factor"); if (str) ff = strtol(str); g_free(str);
i've read all your email, and it looks like mostly enough to get me started, but i just had this thought:
if the dpi reads all the rc files in, we're going to have to be able to specify which rc file we want to get our config from. we need to implement a system of scope for the rc files. i don't want the cookie module asking if it has permission to authorize a site to use cookies by getting it's config from the cacherc which has an identical format.
what do you think is the best way to go about doing that? make the rc filename a requirement in the call?
str = a_Prefs_get("font_factor", "dillorc");
This is a good idea to start with.
and then in the dpi just have the rc files as a linked list with an entry for the filename to do a strcmp() on?
Maybe, but remember that cookiesrc has another format. It's not a variable/value pairs list, but a list of instances of the same abstract variable (to name it somehow ;). This also needs some thought.
also, i still need to read about dpis of course, but are they long running processes?
Dpi servers, YES. Dpi filters come and go per request.
the way i'm thinking is that we don't want the rc files read every time a preference is needed, so the first instance of dillo will start the config dpi running, and it will continue to run until there are no more instances of dillo running. does this sound reasonable?
Yes. In fact, that's what the bookmarks dpi server does. You don't even have to worry about launching a dpi, that's the dpid job. It's done automatically. -- Cheers Jorge.-