Profile Map enables arbitrary profile fields to be mapped to a fixed data model in the $user object so that third-party modules can easily access the profile data. The module provides callbacks when the mapped profile fields are changed, for example, to require a form to be resubmitted on an address change.
The REST Provider module provides a simple framework for creating RESTful web services using Drupal. It strives to be simple and unobtrusive, imposing as few constraints on developers as possible. Developers are free to create any kind of RESTful web service, not just "Drupalesque" services. This module also takes care of some of the more tedious aspects of creating a RESTful web service.
There are currently three other REST-related modules for Drupal. Here's how this module compares to those:
Project Access is an experimental access control module for use with Project and Project issue tracking.
It allows the settings of access permissions on a per-project basis, both per user and per role.
This module will create an API to allow integration between Drupal and OpenLaszlo, available at http://openlaszlo.org. Required XML files will be generated according to theming needs, allowing for OpenLaszlo flash files to be created on the fly. Requires tomcat to be installed on the server.
This small module provides a simple API and should not be installed unless required by another module, or for your personal development.
Handlers are objects that are called to "handle" various pieces of an API in a swappable manner.
Handlers implement pluggable subsystems in a flexible, extensible manner.
Handlers solve the "many to one" type of extensibility, just has hooks solve the "one to many" sort.
Handlers are easily unit-testable.
Handlers require PHP 5.2.
Handlers will be demoed at DrupalCon Szeged.
Part of the core Drupal API (originally part of the forms API, but also used for rendering structured content that isn't a form) is the drupal_render function. This recursively iterates through the element tree, theming the inside of each element based on the #theme property (if present) of that element.
This module uses functionality available only in PHP 5 or later. It also requires the InnoDB engine as MyISAM tables do not support transactions. There is now a release for Drupal 6, but it has been only minimally tested.
This module supersedes and replaces the original pressflow_transaction module which is now deprecated. This implementation provides a legacy API for drop-in compatibility with code that relied on the previous module.
Transaction provides a nested transaction API modeled after Java's synchronized functions. This makes using transactions easy because there is no need to worry about transaction "garbage collection" like running COMMIT or ROLLBACK just before the function returns. This module also protects against the hazards of nested transactions and partial ROLLBACKs.
This module (loosely based on the Vote up/down Package) allows voting on project issues. It depends on the Project issue tracking and Voting API modules.
