Issue 30 in salmon-protocol: magic_public_keys should be changed to magic_keys

11 views
Skip to first unread message

salmon-...@googlecode.com

unread,
Jan 20, 2011, 5:03:43 PM1/20/11
to salmon-...@googlegroups.com
Status: New
Owner: johnrobertpanzer

New issue 30 by charlie....@gmail.com: magic_public_keys should be changed
to magic_keys
http://code.google.com/p/salmon-protocol/issues/detail?id=30

section 8.2.3, '"magic_public_keys" array' is referenced instead
of '"magic_keys" array'


salmon-...@googlecode.com

unread,
Jan 21, 2011, 3:23:58 PM1/21/11
to salmon-...@googlegroups.com
Updates:
Status: Accepted

Comment #1 on issue 30 by johnrobertpanzer: magic_public_keys should be

Check. Actually I think the better name is to use throughout
is "magic_public_keys", as it's less ambiguous and less collision-prone.
Are there implementors who need to change though? Or should we just stick
with magic_keys?

salmon-...@googlecode.com

unread,
Jan 21, 2011, 5:08:35 PM1/21/11
to salmon-...@googlegroups.com

Comment #2 on issue 30 by charlie....@gmail.com: magic_public_keys should

I don't have or know of any implementations of the json keys
serialization. "magic_public_keys" sounds good to me.

Reply all
Reply to author
Forward
0 new messages