On Tue, Nov 22, 2011 at 10:29 PM, Stephan Beal <sgb...@googlemail.com>wrote:
> On Tue, Nov 22, 2011 at 10:10 PM, Jeremy Cowgar <jer...@cowgar.com> wrote:
>
>> That does indeed work
>>
>
> PS: on Thursday morning i'll be leaving town for the back woods of
> northern Germany for 4 days (without a PC), so i'll get the cookie name
> added to the JSON output tomorrow (Wednesday) evening before i leave.
>
i forgot to mention that i have a horrible disease called, "can't sleep
when there's an easy bug which can be fixed."
i've got the code in place but i'm undecided on the JSON-side name of the
login key. i'm hesitant to use the word "key" in the name because i want to
avoid any potential confusion with "API key" and the like. The auth token
value is called authToken, and i'm very hesitant to change that because
it's already used in many, many places (more in docs than code).
So now the 64kb question is: if the cookie's _value_ is called
"authToken", what should the cookie's _name_ be called? i apologize that i
wasn't foresightful enough in advance to realize that the cookie's name
might be useful in the JSON API (because it's effectively random, there
didn't seem to be much use for it).
e.g.:
"payload":{
"authToken":"2D0E..../json-demo",
"whatGoesHere???": "fossil-ABCDDCBA", // project-specific value
...
"name":"json-demo",
"capabilities":"hgjorz"
}
--
----- stephan beal
http://wanderinghorse.net/home/stephan/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
