We were recently approached by a client who wanted to create two sites to serve different audiences but with vast amounts of common content. The same group of people would be responsible for the upkeep of both sites and the desired solution would allow content to be shared with great ease.

I recently attended Drupal Camp Alberta with about another 50 people. The reason for my attendence was that I had been invited to speak about the drupal services module as one of the co-maintainers of the project.

The drupal services module is maintained by myself, Rob Loach and Scott Nelson and has been existence as a drupal module for about 18 months. The module attempts to abstract both servers and services to allow multiple protocols to have to the same data. This opens opportunities for drupal to act as true server and a remote data repository for distripate clients. Services is currently under going active dvelopment and is maturing rapidly as a module. The module ships with a number of services being available:

• Node service. This provides the ability to create, save and delete nodes.
• Search service. This provides the ability to initiate user or node based searches.
• System service. This provides utility functions to get and set variables and re-start connections when using a cookie-less client.

Currently we are carrying out a piece of integration work between Drupal and Salesforce. Drupal is responsible for pulling the data from Salesforce and this achieved by calling the SOQL api via a webservice. The data is returned in a SOAP format. This article assumes you are using this salesforce client

http://sourceforge.net/project/showfiles.php?group_id=96634&package_id=1...