On 2 March 2010 23:04, Ross Gardler <[email protected]> wrote: > On 02/03/2010 16:58, Suhothayan Sriskandarajah wrote: > >> Hi, >> >> I'm willing to implement a java interface to the REST apis with test code >> as >> Ross suggested. >> > > For context Suho and I had a short exchange offlist about potential for > GSoC. > > I informed him that, as long as the ASF is accepted as a mentoring org I > will be willing to mentor at least one participant on Wookie. I also > suggested that engaging with the community prior to GSoC evaluation can > strengthen the aplication considerably. I suggested some assistance with the > connector framework might be appropriate. > > > when i was going through the mailing list i found there was a discussion >> on the current inconsistencies with in the Wookie REST apis and i too >> found a proposed api for Wookie Widget instance. >> > > Ignoring the potential red herring of my criticism of the existing > implementation of the REST API there are two tasks we seem to be in > agreement about: > > - the REST API as specified [1] provides the required features, but is not > very RESTful in design (see [2]) > > - the connector framework only implements a small number of the REST API > > There are two things that can be done here. The first is to design a more > RESTful API and then implement it. This is actually quite a big job and > would be a good candidate for a full GSoC project. > > The implementation of the connector framework can be tackled in small > bite-size chunks. That is, you could select and implement any API call that > is not currently implemented (which is lots of them), such as any of the > properties calls. >
since nothing is implemented in "properties" and as it doesn't have any inconsistencies like" participant" I thought of starting with that. > In terms of exactly how the appropriate call should be implemented should > follow the lead of the existing connector framework [3] and test code [4]. > > here I'm taking other implementations for examples - such as Widget Instances I strongly suggest tackling just a single API method and providing a patch > for that rather than trying to implement many at once. This gives us a > chance to evaluate your design and ensure that we are not duplicating > effort. > ok, i'll keep that "not duplicating" in my mind. > With respect to duplicating effort I will not be doing any work on the > method calls for at least the next week or so. I'm focussing on separating > out the code from the main tree, getting the PHP code into SVN and testing > both in real world environments. If you do start tackling one of the API > methods be sure to drop a note in this thread. > > Don't hesitate to ask if you need more pointers. > since their is no properties class first I'm writing one and then I'll start to implement one of its calls. Suho Ross > > > [1] http://incubator.apache.org/wookie/wookie-rest-api.html > [2] http://markmail.org/thread/wsjb3bqqeshlk26d > > >> Regards, >> Suho >> >> >
