What's the status?

I've just taken this abandoned project over as I had started writing a client API for services. Immediate intention is to create a pluggable API with Drupal services plugin and possibly Flickr plugin. Also example clients:

• FeedAPI - For data imported to the local site as nodes and available for further processing/editing.
• Views 3 - For transient data which you don't want to store locally.

Hello,

I recently come up with a similar idea, i.e. to write clients APIs for services module,
And during preliminary research I found your project :)

Now looking to check what you have so far, i.e. code, ideas, etc.
the code under CSV looks a little outdated... is it everything you have done so far or maybe using another SCM like git, etc.?

Let me know.

Thanks.

I have a completely new version in development. It's a very early prototype so I haven't got any code here yet - I expect to get some code here (but not a release) in the next couple of weeks. So far I have at basic proof of concept stage for d6:

• A clients API module. This allows pluggable backend modules for different service types and handles basic admin of adding named services. It also provides a very simple single interface for clients to code against which allows them to use any of the installed services.
• A Drupal Services backend. This is coded against an older version of 6.x-0 services in a closed environment and is hardcoded to use services key + login settings so will need some work against more current versions.
• A FeedAPI client. This is at a very early stage but I've got a basic working demo including feed element mapping.
• A Views 3 client. Some exploratory code done but the basic mechanics were working and this seems to be doable.

The aim is that it will ship with a couple of backends - Drupal Services and probably Flickr (so it has a simple REST example as well as token-authenticated XML-RPC) and a couple of clients covering importing to local node (i.e. FeedAPI) and simple redisplay (i.e. Views). Then any new service backends will automatically plug into the clients and any new clients will transparently be able to access the services.

A couple of things in particular which haven't been started are oauth for the clients API module and a client for the new Feeds module. There is also d7. Let me know if you'd be up for working on any of those.

@adub, thanks for the reply :)

I was writing the xml-rpc client and service module for particular needs.

And however the services module already makes it simply to write services, I quickly realize that it would be nice to have similar approach for clients modules, i.e. got the same idea as you have for "clients API module". Then I found your project and interesting to check what architecture you come up with :)

I've committed some very early code. This includes a sub-module for connecting this api and management tool to drupal services. The aim is for these backends to be easy to write and encourage contribution - they are overcomplex at the moment and this will need some attention. When that's a bit more stabilised, they would probably be set up as separate projects rather than as sub-modules to this.

I've also set up another project - clients_feedapi - which is where to find a feedapi client that implements this interface. However, the js file included with that project won't work as is and will need some adjustment.

This module suite would probably benefit from a screencast.

Just a quick update for anyone following this. The code currently in CVS is in the process of being extensively re-engineered. The biggest functional change is that I am moving service configurations from the end clients into this module. This means that clients are much more lightweight and simply choose a configuration that has been defined in the clients module.

In addition, due to the pace of development on the Feeds module and deprecation of FeedAPI, this will ship with a Feeds client but not FeedAPI - these can coexist so existing FeedAPI users can use a Clients/Feeds combination without any issue.

This is now available on the project home page. Any contributions appreciated.

Closing this issue as this project has moved along quite a lot and is a bit more ready for some (tentative) testing. Would really appreciate feedback/bug reports at this stage.