Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
Elgg development
Home
+ new post
About this group
Join this group
Message from discussion Survey on Elgg's REST api
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
milan  
View profile  
 More options Oct 23 2009, 7:15 am
From: milan <mi...@magudia.com>
Date: Fri, 23 Oct 2009 04:15:46 -0700 (PDT)
Local: Fri, Oct 23 2009 7:15 am
Subject: Re: Survey on Elgg's REST api
Print | View thread | Show original | Report this message | Find messages by this author
1) Yes - I think we are, but not open sourced api's

2) Created elgg based web services

3) See 4!

4) We're using the HMAC signatures or to be accurate we tried to use
them and found them to not be compatible with other tool sets and
languages. The problem I think was that the HMAC was calculated into
hex values and not encoded into a standard canonicalized format which
doesn't change across toolkits.

a) The actually format of the string to sign wasn't normalised to
UTF-8 (not normally an issue, but can be)
b) The hmac isn't generated using binary values (see:
http://php.net/manual/en/function.hash-hmac.php)
c) If the hmac is in binary then the output of this can be base64
encoded into a standard strict format, which is built into nearly
every language by default (apart from *cough* java where you need a
external jar).

Why do this? As other languages by default out put binary values from
the HMAC and also the hex output is generally unpredictably different.

I have an example client here:
http://www.hedgehogs.net/mod/studios/client/php/

We also did away with doing different Hashes for POST and GET.
Basically we had a look at the Amz S3 model and then overloaded the
current API - I think.

As for 5) and 6), i'll ask Sammy as he done more API work than I have!

Milan

On Oct 22, 2:40 pm, Cash Costello <cash.coste...@gmail.com> wrote:

> Hi, Antoine

> If you're just starting out, I recommend grabbing the latest REST api
> from svn because it has a lot of bug fixes. The files you need are:

> /engine/lib/api.php
> /engine/lib/pam.php
> /engine/lib/xml.php
> /languages/en.php (error messages)
> /services/api/rest.php

> Note that api.php has a hook into Elgg's new unit testing framework
> but you won't be able to use that without grabbing more files from
> svn. Also, currently the schema in SVN has a bug which breaks the
> activity river.

> Cash

> On Oct 22, 5:49 am, Ant- <antoine.raba...@gmail.com> wrote:

> > Hi Cash and everybody.
> > to answer your survey:

> > 1) No but it's a project

> > 2) iPhone and adroid application

> > 3) not yet but I will implement it

> > 4) just setting that up right now :)


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google