REST

I'm trying to figure out the best way to handle images in a headless drupal 8 install. Using the /entity rest endpoint is not working during serialization as it seems like I need to have a URI for the existing file on the drupal install. I'd like to be able to do everything in one step, if that's possible.

I've stumbled across some older, but still very interesting articles by Kurt Cagle regarding combining Drupal and XML technologies:

• Drupal as Open Architecture
• XProc: Drupal, XML Pipelines and RESTful Services
• http://news.oreilly.com/kurt-cagle/
• http://www.xmltoday.org
• http://semanticmodeling.blogspot.com

Hi folks

I am writing a Headless Drupal application for Drupal 8 and I found this discussion Putting off PUT https://groups.drupal.org/node/284948

I'm trying to create a patch to enable PUT for entities in order to enable to create a client side node add/update from Backbone https://www.drupal.org/node/2399813

Someone here has more knowledge about this situation or have a contingence plan?

Kind regards,

We held our Broward Drupal monthly meetup on Wednesday, December 10th from 7:00pm to 9:00pm.

Remote participants(via Skype and Join.me):
Orlando - Deborah Wilson, Patricia Mathews
Miami - Ron Norman @rnorman489

In Person (Greater Fort Lauderdale, Broward County Florida):
Carlos Kosloff @asrealty, Jay Epstein @jeppy64 and me @hectoriribarne

Hello Drupal Community,
I and my mentor Jeff Linwood ( https://www.drupal.org/u/jefflinwood ) we are very glad to inform you that GSoC 2014 project - an example iOS application for Drupal 8 has been completed.

As per the requirement we have demonstrated CRUD operation for content entity , login - logout , fetching data from REST export ( for view). Due to file related bug in REST module () we are unable to demonstrate CRUD on file resources. We have used AFNetworking and we have also created same project with NSURLSession API.

Having discovered that Services just can't handle parsing XML correctly (attributes), and that altering the parser list to call simplexml doesn't, in the end, seem to call it, I'm trying my luck with restws, given that it seems to be the direction to head in anyway.

I have configured the path in my module as such:

function mymodule_restws_resource_info() {
 return array(
 'mymodule_person' => array(
 'label' => t('Person'),
 'class' => 'PersonResourceController',
 'menu_path' => 'api/person',
 ),

Hey folks,

Only local images are allowed.

I am happy to announce that the Backbone.js Cookbook I wrote for the PACKT publishing has been finally published. It covers many interesting topics and contains over 80 recipes. You will learn how to creating outstanding Backbone.js application from scratch. Please, check it out!

Also, there are going to be many interesting sessions about Backbone.js and REST on the DrupalCon Prague!

Tuesday:

• EVOLVING FRONTEND DEVELOPMENT; DANCING ON THE TIP OF A HURTLING ROCKET by @jessebeach
• USING BACKBONE.JS WITH DRUPAL 8 & 7 by @dealancer

Wednesday:

• REST AND SERIALIZATION IN DRUPAL 8 by @linclark and @klausi
• BOF: DRUPAL 8, BACKBONE AND REST: BUILDING THE CLIENT-SIDE APPLICATION LAYER

You are welcome!

I've just released a pair of modules I developed while working on our Drupal front-end dashboard for our Drupal support services, which use Redmine at the back. Might be of interest to group members:

API - https://drupal.org/project/redmine_rest_api
And example - https://drupal.org/project/redmine_issues

For those who are interested in the hypermedia part of Web Services, I wanted to call attention to a discussion posted in the WSCCI group, Proposing an alternative to application/vnd.drupal.ld+json.

The discussion is timeboxed to February 26th.

During the WSCCI Web Services Format Sprint last summer, JSON-LD was chosen as the front-runner for primary format. After that, we looked at what features of JSON-LD we would use and what use cases we wanted to support (summarized here).