[openspending-dev] api key
Alberto Rodriguez Peon
alberto.rodriguez.peon at cern.ch
Mon Aug 19 12:07:32 UTC 2013
Yes, I will start implementing the public/private key version. I will do it as generic as possible so if in the future it needs to be changed (for example to OAuth), it won't be very painful.
From: Tryggvi Björgvinsson [tryggvi.bjorgvinsson at okfn.org]
Sent: 19 August 2013 12:14
To: Alberto Rodriguez Peon
Cc: openspending-dev at lists.okfn.org
Subject: Re: [openspending-dev] api key
On mán 19.ágú 2013 10:07, Alberto Rodriguez Peon wrote:
Personally, I think the approach with the public/private key will be the easiest (and fastest) to implement. The main problem is that I have only three weeks and a half left in my internship (and plenty of work to do in the CERN side too!). I think that it is not enough time to implement OAuth.
That's fine. Would you want to implement the public/private key solution? I just thought it might be simpler to do the OAuth one since there are probably a lot of python modules we could tap into (and leave maintenance to those modules) -- no pressure to use it though (only a suggestion).
Technical Lead, OpenSpending
The Open Knowledge Foundation<http://okfn.org>
Empowering through Open Knowledge
http://okfn.org/ | @okfn<http://twitter.com/OKFN> | OKF on Facebook<https://facebook.com/OKFNetwork> | Blog<http://blog.okfn.org/> | Newsletter<http://okfn.org/about/newsletter>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openspending-dev