On Tue, Aug 10, 2010 at 09:20:51AM -0500, Tim Donohue wrote:
> On 8/10/2010 8:27 AM, Bojan Suzic wrote:
> > In regards to HTTP Authentication, I have put it in the wiki and will
> > investigate further how it can be done.
> > For the other authentication methods, I am not sure which ones may be of
On 11/08/2010, at 12:26 AM, Mark H. Wood wrote:
> On Fri, Aug 06, 2010 at 09:59:44AM -0500, Tim Donohue wrote:
>> (1) We noticed that the REST API documentation on the wiki currently
>> doesn't mention anything about Authentication. How is authentication
>> expected to be handled (or being ha
Bojan,
Thanks! Obviously there's a lot of back and forth comments, but that's
a great thing. It means a lot of people are interested in the work and
want to see it move forward.
On 8/10/2010 8:27 AM, Bojan Suzic wrote:
> Hi everybody,
>
> I will give answers and some comments to the previous
Hi everybody,
I will give answers and some comments to the previous posts in this email,
as there are some common points in discussion.
First, I have refreshed wiki page, changed it to be more readable and added
some sections. So interested developers and others are welcomed to check and
comment
On Fri, Aug 06, 2010 at 09:59:44AM -0500, Tim Donohue wrote:
> (1) We noticed that the REST API documentation on the wiki currently
> doesn't mention anything about Authentication. How is authentication
> expected to be handled (or being handled)? Is it just Basic HTTP Auth?
> Is there any
On Sat, Aug 7, 2010 at 10:40 AM, Bojan Suzic
wrote:
>
> Yes you are right, it is not mentioned there. Currently the
> authentication is done simply by providing the user name and password
> as request parameters (e.g. GET /rest/items/1.json?user=xxx&pass=xxx).
> If there is a a need within communi
