Subj : Re: Feature request
To   : mark lewis
From : Wilfred van Velzen
Date : Fri Jan 29 2016 08:42 am

Hi mark,

On 28 Jan 16 09:52, mark lewis wrote to Wilfred van Velzen:
  about: "Feature request":

 WV>> That's equivalent to using CSIDL_APPDATA with SHGetFolderPath().

 ml> never heard of that CSIDL thing until you brought it up...

So you are not a certified microsoft developer? (Me neither) ;-)

 WV>> But when you are running binkd as a daemon I don't think you want to
 WV>> use a users private appdata directory for this, but maybe you should?

 ml> wait, what? are you ""stuck"" on one machine, one person? i certainly do
 ml> not want other folks' mail in my stuff nor do i want mine in their's...
 ml> they can run their own point or node with or without full bbs if they want
 ml> and i'll run mine... long gone are the days where one machine is tasked
 ml> with one job... now those types of things are done per account and
 ml> machines have numerous accounts... each standing alone and separate from
 ml> the others...

You do have a valid point, although I think your usecase is very unlikely. But 
what does happen is that sysops with more than 1 nodenumber (sometimes in 
fidonet, sometimes in different othernets), want to run more than 1 instance of 
binkd with seperate configurations. If they run those in different user 
accounts, you don't want to have those binkd instances look in the same 
location for their default configuration file. So although binkd is a server 
application and can be run as a daemon, APPDATA might be a good place for the 
default binkd configuration file location...

Wilfred.

--- FMail-W32-1.69.10.141-B20151003
 * Origin:  point@work  (2:280/464.112)

.