It's worth it, IMHO, to put your config info into a seperate file. I wrote a script for my former job where they needed real replication, not the hell to configure, broken stuff that NT does. It didn't take me long at all to build a config file, and it means that, when I left, they never have bothered me about that program since (I'm still in regular contact with 'em).
And it has to; servers have an odd habit of changing w/o notice at my old place of work. :)
As far as overhead, what I did was do a file test for last modified (which works on Win95 and NT, in case you needed to know) -- takes but a millsecond, and the benifits are obvious.
Make it easy on your backups (or the persons who come next if you leave), and impress your PHBs ("see, you can edit it too, in a pinch"). :)
In reply to Re: Code versus Config
by Asim
in thread Code versus Config
by Odud
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |