Skip site navigation (1) Skip section navigation (2)

Re: [BUGS] More SSL questions..

From: "Christian Klemke" <Christian(dot)Klemke(at)t-online(dot)de>
To: "pgsql-hackers-win32" <pgsql-hackers-win32(at)postgresql(dot)org>
Subject: Re: [BUGS] More SSL questions..
Date: 2005-01-08 00:01:17
Message-ID: 000801c4f515$2db6a780$4701a8c0@NTBKCKLEMKE (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers-win32

I've been following this discussion for some time now and I think that you 
are losing the focus. I mean, who is your target audience ? How many people 
may be out there who have the technical knowledge to put the correct 
settings in the database config files but do not know how to open and modify 
them just because they do not pop up using simple double clicks ? [The same 
goes for the hidden/not hidden directory discussion, BTW.]

Therefore, I'd like to suggest to consider the following solutions:

1. Use the ".ini" extension. Ini files contain plain text, are associated 
with notepad.exe by default and will show up as "Configuration Settings" in 
the explorer. It doesn't matter if they do not fully comply with the default 
ini file format in case of Postgres, as long as they are not accessed by the 
corresponding special API functions.


2. Use a Postgres specific extension like ".pgconfig" and let the installer 
create a proper file type association. I suppose most Windows users will use 
the installer (and those who don't will know how to handle the files 
manually). Alternatively/Additionally, the installer might also set up a 
link like "Modify configuration file" in the program group associated with a 
"notepad <path><file>" command. The Apache HTTP server installer does 
something similar for its "httpd.conf" file, IIRC. This would also "bypass" 
the hidden directory issue.

What do you think ?

Best regards,

----- Original Message ----- 
From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Gary Doades" <gpd(at)gpdnet(dot)co(dot)uk>; "Bruce Momjian" 
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>; <pgsql-hackers-win32(at)postgresql(dot)org>; 
"Matthew T. O'Connor" <matthew(at)zeut(dot)net>; "Andrew Dunstan" 
<andrew(at)dunslane(dot)net>; "T.J." <tjtoocool(at)phreaker(dot)net>
Sent: Friday, January 07, 2005 11:38 PM
Subject: Re: [pgsql-hackers-win32] [BUGS] More SSL questions..

>  > Perhaps there is another extension that is good for Win32
>but i don't
>> think *.txt is it.
>If there needs to be an extension, the new MS thinking in .NET
>seems to
>favour .config files. Both ASP.NET web applications and windows .NET
>executables are automatically given associated .config files by visual

Well, those are both XML files that follow a very specific schema (and
it's the same schema for both these, except there are of course some
tags not relevant in each one). I don't see the ".net does it" argument
as very powerful unless we go all the way - and we don't want to do

My vote is to either go with .txt - to make it autoopen - or go with no
extension at all (as in unix, except remove the initial dot that makes
the whole filename into the extension).


---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?


In response to


pgsql-hackers-win32 by date

Next:From: Andrew DunstanDate: 2005-01-08 00:20:30
Subject: Re: [BUGS] More SSL questions..
Previous:From: Magnus HaganderDate: 2005-01-07 22:58:30
Subject: RC4 MSI is up...

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group