[JDEV] Standards

[William Ahern]

>   Your opinion.  The 'long wrong' as you put it, is the way it's been for 
> nearly 30 years, and no ones right/wrong.  Your method also causes 'data 
> stagnation', aka, if it's ALWAYS in the config file, and I can move it around, 
> when do I actually have to enter my username/password?  Not to mention, it also 
> leads to the issue of what happens when someone get's their hands on that file, 
> eh?  Full access..  ;-P
> 
oops. i meant to say 'long run'. anyhow, admittedly i'm not much of a
programmer (just web sites and trying to learn java), but it would seem to me
that a better way would be to abstract the config in someway. if everybody goes
there own route, we'll end up w/ a ton of different features for different
clients. 

plus, if i use client A, then upgrade to client B, it'd be nice if my info would
transfer over easily.... and who said anything about using flat text files for
this stuff...? at the very least it would be nice if clients of the same
platform could understand each other's configs.... 


-- 
William Ahern
MIS, JINSA

---------------------
JINSA Online
http://www.jinsa.org/
---------------------