The Web Services and Context Core Initiative (WSCCI) aims to transform Drupal from a first-class CMS to a first-class REST server with a first-class CMS on top of it. To do that, we must give Drupal a unified, powerful context system that will support smarter, context- sensitive, easily cacheable block-centric layouts and non-page responses using a robust unified plugin mechanism.
Be sure to read the roadmap overview.
Code can be found in the WSCCI sandbox.
Hot issues
Active issues where we need help:
- Drupal Kernel Patch: This is priority one, based on Symfony2.
- Use Symfony2 session handling: We'll need to improve Symfony2 a bit in the process, too.
- WebSockets: How do we do that in PHP? Or do we?
Key discussions
Important discussions for background:
Recent discussions
WSCCI Web Services Format Sprint Report
A small team met in Paris at the office of Commerce Guys from June 3-5th to discuss Drupal's web services serialization and syndication format needs. In short, "OK, we are going to have all of this fun new routing capability, now what do we do with it?" More specifically, how do we go about serializing Drupal data for consumption by remote programs (either other Drupal sites as in the case of content staging, other non-Drupal sites, client-side applications, or mobile apps), and what protocols and APIs do we make available to manipulate that data?
In attendance were:
- Larry Garfield, WSCCI Lead
- Wolfgang Ziegler, Entity maintainer
- Dick Olsson, Deploy maintainer
- Damien Tournoud, Core generalist and gracious host
- Alex Bronstein (via skype), Core generalist
The raw notes from the sprint are available as a Google Doc, but as usual are rather disjoint and likely won't make sense if you weren't there. A more complete report is below.
Read moreSerialized Data Format Evaluation: CMIS
Status: This evaluation is currently in process. Please add any additional information or correct as you are able. If correcting, please also post a comment with the grounds for the correction.
TL;DR: CMIS is a powerful domain model complemented with extensive bindings for XML and, recently, JSON services. Undertaking a CMIS server implementation on Drupal would be a very, very large and complicated project.
Read moreCore Initiative Windsprints
We will hold windsprints (mini sprints) each week on IRC in #drupal (on irc.freenode.net).
Timezone conversion: Friday, 17:00 to 19:00 UTC
Objectives
- Bring lessons learned from core mentoring hours to Drupal 8 Core Initiatives.
- Provide a structured time where anyone can contribute to core initiatives.
- Leverage an army of potential contributors who don't know where to start.
The Plan
Read moreComparison of HTTP Client Libraries
Coming from this issue on d.o: Evaluate third party libraries to replace drupal_http_request() and the browser in DrupalWebTestCase
Definitions listed in order of importance (top is important).
Parallel Requests: Project uses curl_multi_select(), stream_select(), or socket_select() when issuing multiple requests.
Alternative REST Implementations
From what I understand, Symfony2 is going to be default implementation for RESTful services. That said, Drupal has always prided itself for providing alternatives.
Can REST implementation be pluggable? Say, I would like to integrate: http://zaphpa.org/ as a REST implementation for D8, should I be able to?
Thank you.
Read moreCombined Drupal 8 Initiatives Windsprint (Mini Sprint)
We will hold windsprints (mini sprints) each week on IRC in #drupal (on irc.freenode.net).
Timezone conversion: Friday, 17:00 to 19:00 UTC
Objectives
- Bring lessons learned from core mentoring hours to Drupal 8 Core Initiatives.
- Provide a structured time where anyone can contribute to core initiatives.
- Leverage an army of potential contributors who don't know where to start.
The Plan
Read moreWSCCI Serialized Data Format Evaluation Stub
This is a proposed "stub" page for evaluations of serialization formats proposed as candidates for the core-supported format in the WSCCI initiative.
For Background on the project of researching proposed formats, see the initial reportback from some preliminary research and the "Call to Help" post, in which the proposed task list for WSCCI was laid out.
General Information
Provide a short overview of the format here, to come before the summary break.
Read moreWSCCI Serialization Format Comparison Overview
This page will hold a matrix summarizing the evaluations of various "short-list" candidates for the core-supported serialization format, as well as links to each individual format evaluation page.
For the time being, however, is consists of the general evaluation objectives (requirements and desired functionality) as well as a link to the stub evaluation page (coming as soon as this is posted) and some additional requirements.
Please do participate with edits and comments as you wish.
Read moreWSCCI Serialization Format Preliminary Report-Back
Summary
After an initial review of each of the initial proposed serialization formats proposed by Crell for consideration as the canonical representation format for the WSCCI projects' work, I recommend we focus on CMIS, HAL and JSON-LD for further in-depth evaluation. These projects are sufficiently mature and active, and have (or are actively developing) well-supported open source libraries in PHP and JavaScript with engaged community participation. Other formats reviewed included OData, JSOP, WRML and Collection+JSON, however each of these were marked by issues with available PHP/JS libraries, lack of active development community, immaturity, inactivity, and/or insufficient features.
Read more


