# Gavin Andresen
# 2010-07-19 16:58:48
# https://bitcointalk.org/index.php?topic=461.msg4284#msg4284

@s{quotedtext}
@s{quotedtext}
You ask hard questions!  Most common: probably @p{(link}Windows INI@p{link)} files, because Windows is most common OS. @p{par}

I'd lobby for using JSON; it's (mostly) a subset of YAML (which is a common choice for config files), so any JSON or YAML parser will read it. @p{brk}

@s{quotedtext}
@s{quotedtext}
I think the only big advantage is that it keeps authentication where it belongs in the transport layer, so if, in the future, you @p{(bf}do@p{bf)} want to go with full-fledged HTTPS with certificates the API doesn't have to change. @p{brk}

@s{quotedtext}
@s{quotedtext}
No, I just confused "command" with "parameter", and did this: @p{par}


Code:
@s{gt} bitcoind help @p{brk}
error: First parameter must be the password. @p{brk}
@s{gt} bitcoind @p{lt}my password@s{gt} help @p{brk}
error: unknown command: @p{lt}my password@s{gt} @p{brk}
@s{gt}bitcoind help @p{lt}my password@s{gt} @p{brk}
 ... that works. @p{brk}

 @p{brk}