IPCse11 Nicolas Pastorino Launching content in mobility with REST and eZ Publish

Launchingcontent inmobility withREST & eZ Publish

Launchingcontent inmobility withREST & eZ Publish Nicolas Pastorino - nfrp@ez.no Director Community - eZ Systems @jeanvoye - http://share.ez.no

#ipcse11 Launching content in mobility with Mobile REST & International PHP Conference, SE 2011 - Berlin - May 30th eZ Publish Nicolas Pastorino - nfrp@ez.no Director Community - eZ Systems @jeanvoye - http://share.ez.no

Our agenda :

Our agenda :Multichannel : why ?

Our agenda :Multichannel : why ? REST

Our agenda :Multichannel : why ? RESTExtensible REST API

Our agenda :Multichannel : why ? RESTExtensible REST API Demo

Multichannel : why ? 3

How would youfeel playingPacman on asingle, straight lineof dots ?

How would youfeel playing Boring,Pacman on a right ? linesingle, straightof dots ?

Multichannelcontentdistribution isthe real Pacman

Pre-requisites to multichannel distributionNicolas Pastorino - IPCse11 30/05/2011 7

Pre-requisites to multichannel distributionSeparation of layoutand content at the 1content source level Nicolas Pastorino - IPCse11 30/05/2011 7

Pre-requisites to multichannel distributionSeparation of layoutand content at the 1content source levelDo not compromise onuser experience 2 Nicolas Pastorino - IPCse11 30/05/2011 7

Pre-requisites to multichannel distributionSeparation of layoutand content at the 1content source level “The Superman Effect” Aral Balkan, DPC11Do not compromise onuser experience 2 Nicolas Pastorino - IPCse11 30/05/2011 7

Pre-requisites to multichannel distributionSeparation of layoutand content at the 1content source level “The Superman Effect” Aral Balkan, DPC11Do not compromise onuser experience 2 “There is a lot of effort going into improving customer experience. It is key to get consistency across different channels so their experience does not vary” Jim Daviesni Nicolas Pastorino - IPCse11 30/05/2011 7

Pre-requisites to multichannel distributionSeparation of layoutand content at the 1content source level “The Superman Effect” Aral Balkan, DPC11Do not compromise onuser experience 2 “There is a lot of effort going into improving customer experience. It is key to get consistency across different channels so theirHave a single source experience does not vary” Jim Daviesniof content 3 Nicolas Pastorino - IPCse11 30/05/2011 7

Pre-requisites to multichannel distributionSeparation of layoutand content at the 1content source level “The Superman Effect” Aral Balkan, DPC11Do not compromise onuser experience 2 “There is a lot of effort going into improving customer experience. It is key to get consistency across different channels so theirHave a single source experience does not vary” Jim Daviesniof content 3 “Publishers usually cant afford a dedicated editorial team per channel” Nicolas Pastorino - IPCse11 30/05/2011 7

Are 3rules of thumbenough ?

Are 3rules of thumbenough We’re ? hardly off the ground. Let’s dig further...

SingleContentSource / CMS

Monetized Content StreamsSingleContentSource / CMS

Monetized Content Streams Mobile ApplicationsSingle / Smartphones, TabletsContentSource CMS

Monetized Content Streams Mobile ApplicationsSingle / Smartphones, TabletsContentSource CMS Push 3rd party CRM, ERP Content Newsletters

Monetized Content Streams Mobile ApplicationsSingle / Smartphones, TabletsContentSource CMS Push 3rd party CRM, ERP Content Newsletters Print Legacy publication chains

Monetized Content Streams Mobile ApplicationsSingle / Smartphones, TabletsContentSource CMS Push 3rd party CRM, ERP Content Newsletters Print Legacy publication chains Social Media

"Multichannel media consumers have higher levelsof engagement than those present in only onechannel.The more one watches TV, listens to the radio,spends time online, etc., the more advertising theyconsume.This shows that multichannel contentdistribution will also have an important impacton the publishers revenue structure. It willevolve to become a competitive, critical, enablingtechnology for marketing communications."

Having a REST ? :)

Having a REST ? :) A touch more of insight will help...

“Media companies as well as consumer brands mustrecognize that adding mobile to the multichannel mixdoes not mean creating a mini-channel. Thosebuilding mobile strategies should recognize that: • Mobile is not just about shrinking the desktop experience, • The user environment is an element of the mobile experience, • Mobile users are not simply a subset of online users – some are new.”

Least CommonDenominator :

Least CommonDenominator :a REST API

Thosewere thebasics toincrease your REACH through multiplechannels

REST 15

REpresentationalStateTransfer

REpresentationalStateTransferREST is a set of principles that define how Web standards, such asHTTP and URIs, are supposed to be used.• Give every “thing” an ID• Link things together (“HATEOAS”)• Use standard methods• Resources with multiple representations• Communicate statelessly

REpresentationalStateTransferREST is a set of principles that define how Web standards, such asHTTP and URIs, are supposed to be used.• Give every “thing” an ID• Link things together (“HATEOAS”)• Use standard methods• Resources with multiple representations• Communicate statelessly h"p://www.infoq.com/ar4cles/rest-‐introduc4on h"p://en.wikipedia.org/wiki/Representa4onal_State_Transfer

REpresentationalStateTransfer h"p://www.infoq.com/ar4cles/rest-‐introduc4on h"p://en.wikipedia.org/wiki/Representa4onal_State_Transfer

REpresentationalStateTransferKey goals of REST include:• Scalability of component interactions• Generality of interfaces• Independent deployment of components• Intermediary components to reduce latency, enforce security andencapsulate legacy systems h"p://www.infoq.com/ar4cles/rest-‐introduc4on h"p://en.wikipedia.org/wiki/Representa4onal_State_Transfer

Extensible REST APIat the core of the eZ Publish CMS 18

At the core of the eZ Publish CMSExtensible REST API REST as a core featureNicolas Pastorino - IPCse11 30/05/2011 19

At the core of the eZ Publish CMSExtensible REST APIDedicated front-controllerNicolas Pastorino - IPCse11 30/05/2011 20

At the core of the eZ Publish CMSExtensible REST API REST setup REST eZP REST request FC eZ Publish web-‐requestNicolas Pastorino - IPCse11 30/05/2011 21

At the core of the eZ Publish CMSExtensible REST API Mapping content into resourcesNicolas Pastorino - IPCse11 30/05/2011 22

At the core of the eZ Publish CMSExtensible REST API Makes data availableNicolas Pastorino - IPCse11 30/05/2011 23

At the core of the eZ Publish CMSExtensible REST API Makes data reusableNicolas Pastorino - IPCse11 30/05/2011 23

At the core of the eZ Publish CMSExtensible REST API Content is essentially liberatedNicolas Pastorino - IPCse11 30/05/2011 24

At the core of the eZ Publish CMSExtensible REST API URI patternNicolas Pastorino - IPCse11 30/05/2011 25

At the core of the eZ Publish CMSExtensible REST API Just a token to trigger your rewrite rule Call + GET Host / Preﬁx / Provider / Version / params ezpRestPreﬁxFilterInterfaceNicolas Pastorino - IPCse11 30/05/2011 26

At the core of the eZ Publish CMSExtensible REST API Preﬁx Just a token to trigger your rewrite ruleProvider ezpRestPreﬁxFilterInterfaceVersionNicolas Pastorino - IPCse11 30/05/2011 26

Prefix filterezpRestPrefixFilterInterfaceCurrent providerCurrent parsed version valueNicolas Pastorino - IPCse11 30/05/2011 27

Versioned APIclass ezpRestRouter extends ezcMvcRouter{ public function createRoutes() { // ezpRestApiProvider $routes = array( new ezcMvcRailsRoute( /content/node/:nodeId/listAtom, ezpRestAtomController, collection ), new ezcMvcRailsRoute( /content/node/:nodeId/list, ezpRestContentController, list ), new ezcMvcRailsRoute( /content/node/:nodeId, ezpRestContentController, viewContent ), new ezcMvcRailsRoute( /content/node/:nodeId/fields, ezpRestContentController, viewFields ), new ezcMvcRailsRoute( /content/node/:nodeId/field/:fieldIdentifier, ezpRestContentController, viewField ), new ezcMvcRailsRoute( /content/object/:objectId, ezpRestContentController, viewContent ), new ezcMvcRailsRoute( /content/object/:objectId/fields, ezpRestContentController, viewFields ), new ezcMvcRailsRoute( /content/object/:objectId/field/:fieldIdentifier, ezpRestContentController, viewField ), new ezpRestVersionedRoute( new ezcMvcRailsRoute( /foo, myController, myActionOne ), 1 ), new ezpRestVersionedRoute( new ezcMvcRailsRoute( e/foo, myController2 or myControlerWhichExtendsmyController, myBetterAndScalingAction ), 2 ), ); return ezcMvcRouter::prefix( /api, $routes ); }} Nicolas Pastorino - IPCse11 30/05/2011 28

Versioned APIezpRestVersionedRoute Version makes the notion version a part of the routing decisionNicolas Pastorino - IPCse11 30/05/2011 29

At the core of the eZ Publish CMSExtensible REST API Build your own ﬂavor, extend the interface(s)Nicolas Pastorino - IPCse11 30/05/2011 30

Extending the interface REST providersNicolas Pastorino - IPCse11 30/05/2011 31

Extending the interfaceezpRestProviderInterfaceNicolas Pastorino - IPCse11 30/05/2011 32

Overview of hooksthe places where you can go wild.

Nicolas Pastorino - IPCse11 30/05/2011 34

Route setup - Exampleclass ezpRestRouter extends ezcMvcRouter{ public function createRoutes() { $providerRoutes = ezpRestProvider::getProvider( ezpRestPrefixFilterInterface::getApiProviderName() )->getRoutes(); $routes = array( new ezpMvcRailsRoute( /fatal, ezpRestErrorController, show ), new ezpMvcRailsRoute( /http-basic-auth, ezpRestAuthController, basicAuth ), new ezpMvcRailsRoute( /login/oauth, ezpRestAuthController, oauthRequired ), new ezpMvcRailsRoute( /oauth/token, ezpRestOauthTokenController, handleRequest), // ezpRestVersionedRoute( $route, $version ) // $version == 1 should be the same as if the only the $route had been present new ezpRestVersionedRoute( new ezpMvcRailsRoute( /foo, myController,myActionOne ), 1 ), new ezpRestVersionedRoute( new ezpMvcRailsRoute( /foo, myController,myActionOneBetter ), 2 ), ); return ezcMvcRouter::prefix( /api, array_merge( $providerRoutes, $routes ) ); }} Nicolas Pastorino - IPCse11 30/05/2011 35

Extensible REST APIKey features 36

Key featuresExtensible REST API Content resourcesNicolas Pastorino - IPCse11 30/05/2011 37

Key featuresGET /[api]/v1/content/object/ <objectId>/fields HTTP/1.1Nicolas Pastorino - IPCse11 30/05/2011 38

Key featuresfields/<fieldname> type (datatype string) identifier (attribute identifier) value (string representation of data) id (object attribute numerical ID) classattribute_id (class attribute numerical ID)Nicolas Pastorino - IPCse11 30/05/2011 39

Key features GET /[api]/v1/content/object/ <objectId>/field/ <FieldIdentifier> HTTP/1.1Nicolas Pastorino - IPCse11 30/05/2011 40

DemoWeb + Android, eZ Publish powered 41

Famous Last Slides 42

RECAPMultichannel : why ? RESTExtensible REST API Demo

You won’t everplay Pacmanthe same wayagain :)

Find me on Twitter : @jeanvoyeRate this talk : http://joind.in/3482Slides available soon at http://slideshare.net/jeanvoyeeZ Conference, June 16th&17th, London : Rasmus Lerdorf, Derick Rethans, Tobias Schlitt Get a 20% off coupon at the eZ booth in the hall, and register : http://london2011.ez.noeZ Communityhttp://share.ez.noeZ Publish Community Projecthttps://github.com/ezsystems/ezpublish Thank you !http://share.ez.no/downloadhttp://share.ez.no/get-involvedeZ Systems & eZ Publish Enterprise Editionhttp://ez.no

IPCse11 Nicolas Pastorino Launching content in mobility with REST and eZ Publish

by Nicolas Pastorino on May 30, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

1 Embed 1

Statistics

IPCse11 Nicolas Pastorino Launching content in mobility with REST and eZ Publish — Presentation Transcript