-
Notifications
You must be signed in to change notification settings - Fork 4
/
Copy pathresting-with-symfony2.html
956 lines (843 loc) · 42.2 KB
/
resting-with-symfony2.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
<!DOCTYPE html>
<html>
<head>
<title>RESTing with Symfony2 | Lukas Kahwe Smith</title>
<link rel="stylesheet" href="css/sfcon2k13/reveal.min.css">
<link rel="stylesheet" href="css/sfcon2k13/serif-theme.css" id="theme">
<link rel="stylesheet" href="css/sfcon2k13/zenburn.css">
<link rel="stylesheet" href="css/sfcon2k13/pageNumbers.css">
<link rel="stylesheet" href="css/sfcon2k13/custom.css">
<script>
document.write('<link rel="stylesheet" href="css/sfcon2k13/' +
(window.location.search.match(/print-pdf/gi) ? 'pdf' : 'paper') +
'.css" type="text/css" media="print">'
);
</script>
</head>
<body>
<div class="reveal">
<div class="slides">
<section>
<h1 class="title">RESTing with Symfony</h1>
<em>Lukas Kahwe Smith - October 10th, 2014</em>
</section>
<section>
<section>
<h1 class="title">Introduction to REST</h1>
</section>
<section data-markdown>
## REST, hurray!
</section>
<section data-markdown>
## REST, but why?
</section>
<section data-markdown>
## **Everyone** who has ever talked about REST, at some point **has said something idiotic about REST**.
Except for maybe Roy Fielding.
</section>
<section data-markdown>
## For example, I once thought it meant **converting all GET parameters to virtual directories**. Differentiating GET and POST parameters seemed like overzealous academics.
</section>
<section data-markdown>
## I only **began to understand why REST** really makes sense and what REST it is really about **when I started looking into cache headers and reverse proxies**.
</section>
<section data-markdown>
## **REST** is all about leveraging HTTP and **constraining your application to a set of rules**, so that **users** of your API **can safely apply assumptions** about the behavior of your application.
</section>
<section data-markdown>
<script type="text/template">
## HTTP Request Anatomy
```
GET /app_dev.php/notes HTTP/1.1
Host: symfony-rest-edition.lo
Accept: application/json;q=0.9,*/*;q=0.8
Content-Type: application/json
Content-Length: length
```
</script>
</section>
<section data-markdown>
<script type="text/template">
## HTTP Response Anatomy
```
HTTP/1.1 200 OK
Allow: GET, POST
Cache-Control: max-age=15, public, s-maxage=30
Content-Type: application/json
Date: Wed, 15 Jan 2014 15:09:01 GMT
Last-Modified: Wed, 15 Jan 2014 14:09:03 GMT
Server: Apache/2.2.24 (Unix) DAV/2 PHP/5.4.20 mod_ssl/2.2.24 OpenSSL/0.9.8y
Vary: Accept-Encoding,Accept-Language
{"notes":["a","b","c"]}
```
</script>
</section>
<section data-markdown>
<script type="text/template">
## Rest Maturity Model
<p>
<small>
[http://martinfowler.com/articles/richardsonMaturityModel.html](http://martinfowler.com/articles/richardsonMaturityModel.html)
</small>
</p>
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
## RMM Level 0
* Aka "The Swamp of POX"
* HTTP as a tunneling mechanism
* "Procedural" communication (RPC)
* Single endpoint (per operation)
</script>
</section>
<section data-markdown>
<script type="text/template">
## RMM Level 0
<p>
<small>
[http://martinfowler.com/articles/richardsonMaturityModel.html](http://martinfowler.com/articles/richardsonMaturityModel.html)
</small>
</p>
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
## RMM Level 1
* Aka "Resources"
* Individual resources, i.e. URIs
* "Object orientated" communication
</script>
</section>
<section data-markdown>
<script type="text/template">
## RMM Level 1
<p>
<small>
[http://martinfowler.com/articles/richardsonMaturityModel.html](http://martinfowler.com/articles/richardsonMaturityModel.html)
</small>
</p>
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
## RMM Level 2
* Aka "HTTP Verbs"
* Client uses specific HTTP method
* Server uses HTTP status codes
</script>
</section>
<section data-markdown>
<script type="text/template">
## RMM Level 2
<p>
<small>
[http://martinfowler.com/articles/richardsonMaturityModel.html](http://martinfowler.com/articles/richardsonMaturityModel.html)
</small>
</p>
</script>
</section>
<section data-markdown>
<script type="text/template">
## HTTP Verbs
<br /><center>
| Method | Safe | Idempotent |
|:------:|:----:|:----------:|
| GET | yes | yes |
| HEAD | yes | yes |
| POST | no | no |
| PUT | no | yes |
| DELETE | no | yes (*) |
| .. | no | no |
</center>
</script>
</section>
<section data-markdown>
<script type="text/template">
## Safe vs. Idempotent
* Safe means cacheable
* Idempotent: result independent on the # of executions
* (*) There is a debate if DELETE should be idempotent or not,
ie. what should be the response for a DELETE requests on a non existent resource?
</script>
</section>
<section data-markdown>
<script type="text/template">
## HTTP Status Codes
<br /><center>
| Code range | Description | Example |
|:----------:|:-------------:|:-----------------------:|
| 1xx | Information | 100 - Continue |
| 2xx | Successful | 201 - Created |
| 3xx | Redirection | 301 - Moved Permanently |
| 4xx | Client Error | 404 - Not Found |
| 5xx | Server Error | 501 - Not Implemented |
</center>
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
## RMM Level 3
* Aka "Hypermedia Control"
* Service discovery via link relations
* ATOM, HAL, JSON-LD, IANA Link Rel
</script>
</section>
<section data-markdown>
<script type="text/template">
## RMM Level 3
<p>
<small>
[http://martinfowler.com/articles/richardsonMaturityModel.html](http://martinfowler.com/articles/richardsonMaturityModel.html)
</small>
</p>
</script>
</section>
<section data-markdown>
<script type="text/template">
<h1 class="title">*H*ypertext *A*s *T*he *E*ngine *O*f *A*pplication *S*tate</h1>
<h1 class="title">=</h1>
<h1 class="title">HATEOAS</h1>
</script>
</section>
<section data-markdown>
<script type="text/template">
## RMM vs REST vs real life
* Most developers consider RMM Level 2 sufficient for REST
* RMM Level 3 is a precondition but not sufficient for REST
* ie. RMM only covers a subset of what REST requires
* RMM Level 3 makes URI formatting matter less
</script>
</section>
<section data-markdown>
<script type="text/template">
## RMM vs REST vs real life
* Browsers are bad REST clients
* REST is protocol independent
* Few (no?) clients really leverage HATEOAS
</script>
</section>
</section>
<section>
<section>
<h1 class="title">Content Negotiation</h1>
</section>
<section data-markdown>
<script type="text/template">
## Unified Resource Identifier
* URIs identify resources
* URIs are format independent
* URI "file extensions" != RESTful
</script>
</section>
<section data-markdown>
<script type="text/template">
## Media Types
* Identifies a representation format
* Custom types use `application/vnd.[XYZ]`
* Used inside the `Accept` / `Content-Type` headers
<br><center>
| Header | Description |
| ------------ |---------------------------------|
| `Content-Type` | HTTP message format |
| `Accept` | HTTP response format preference |
</center>
</script>
</section>
<section data-markdown>
<script type="text/template">
## Content Negotiation
* Finding appropriate response format
* **No standardized algorithm available**
* Apache [mod_negotiation](http://httpd.apache.org/docs/2.4/content-negotiation.html) algorithm is documented
* Also covers encoding (`Accept-Encoding`) and language (`Accept-Language`) negotiation
</script>
</section>
<section data-markdown>
<script type="text/template">
## Example
```
Accept: application/json, application/xml;q=0.9, text/html;q=0.8,
text/*;q=0.7, */*;q=0.5
```
<br /><center>
| Priority | Description |
| -------- |-------------------------------------|
| `q=1.0` | `application/json` |
| `q=0.9` | `application/xml` |
| `q=0.8` | `text/html` |
| `q=0.7` | `text/*` (ie. any text) |
| `q=0.5` | `*/*` (ie. any media type) |
</center>
</script>
<section>
<h1 class="title">So much for the REST theory ..</h1>
</section>
</section>
</section>
<section>
<section>
<h1 class="title">So let us get started .. </h1>
</section>
<section>
<h1 class="title">.. on RESTing with Symfony2</h1>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
## JMSSerializerBundle
</script>
</section>
<section data-markdown>
<script type="text/template">
## In A Nutshell
* Integrates the JMS Serializer library with Symfony2
* Enables (de)**serialization of object graphs**
* Implements visitor pattern to enable flexibility
* Fully leverage native JSON and XML
* Custom **exclusion strategies** to determine what to serialize
</script>
</section>
<section data-markdown>
<script type="text/template">
## Usage
```
use JMS\SerializerBundle\Annotation as Serializer;
/** @Serializer\XmlRoot("response") */
class MyResponse
{
/** * @Serializer\XmlList(inline=true, entry="article") */
protected $articles;
/** * @Serializer\XmlAttribute() */
protected $page;
public function __construct(Collection $articles, $page)
{
$this->articles = $articles;
$this->page = $page;
}
}
```
</script>
</section>
<section data-markdown>
<script type="text/template">
## JSON
```
{
"articles": [
"bim",
"bam",
"bingo"
],
"page": "2"
}
```
</script>
</section>
<section data-markdown>
<script type="text/template">
## XML
```
<response page="2">
<article>bim</article>
<article>bam</article>
<article>bingo</article>
</response>
```
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
## FOSRestBundle
</script>
</section>
<section data-markdown>
<script type="text/template">
## In A Nutshell
* **Toolbox of services** and listeners to build RESTful APIs
* Generate HTML, XML, JSON from a single action
* Automatic generation of routes from actions
* GET parameter parsing and validation
* Integration with Symfony2 serializer and JMS Serializer
* Integration with SensioFrameworkExtraBundle
* Accept header negotiation
* Request body decoding
* API versioning
</script>
</section>
<section data-markdown>
<script type="text/template">
## View Response Listener and Route Generation
```
class RestController
{
/**
* Get the list of articles
* route name: liip_hello_rest_get_articles
* pattern: /liip/hello/rest/articles.{_format}
* http method requirement: GET
*
* @View()
*/
public function getArticlesAction(Request $request)
{
$page = $request->query->get('page');
$page = preg_match('\d+', $page) ? $page : 1;
$articles = array('bim', 'bam', 'bingo');
return new \Acme\MyBundle\MyResponse($articles, $page);
}
}
```
</script>
</section>
<section data-markdown>
<script type="text/template">
## HTML
```
<html>
<body>
<div>
<div>bim</div>
<div>bam</div>
<div>bingo</div>
</div>
<div>page: 2</div>
</body>
</html>
```
</script>
</section>
<section data-markdown>
<script type="text/template">
## Param Fetcher Listener
```
fos_rest:
param_fetcher_listener: force
```
```
class RestController
{
/**
* Get the list of articles
* route name: liip_hello_rest_get_articles
* pattern: /liip/hello/rest/articles.{_format}
* http method requirement: GET
*
* @View()
* @QueryParam(name="page", requirements="\d+", default="1")
*/
public function getArticlesAction($page)
{
$articles = array('bim', 'bam', 'bingo');
return new \Acme\MyBundle\MyResponse($articles, $page);
}
}
```
</script>
</section>
<section data-markdown>
<script type="text/template">
## MIME Type Listener
* Register MIME types that Symfony2's Request class does not support by default
```
fos_rest:
view:
mime_types:
json: ['application/json', 'application/vnd.example.foo+json']
rss: 'application/rss+xml'
jpg: 'image/jpeg'
png: 'image/png'
jsonp_handler: ~
```
</script>
</section>
<section data-markdown>
<script type="text/template">
## Content Negotiation
```
fos_rest:
format_listener:
rules:
-
path: ^/
priorities: [ html, json, xml ]
fallback_format: ~
prefer_extension: true
```
```
Accept: application/json, application/xml;q=0.9, text/html;q=0.8,
text/*;q=0.7, */*;q=0.5
```
</script>
</section>
<section data-markdown>
<script type="text/template">
## Version Listener
* Parse version information from a media type and automatically set it in JMS serializer
```
fos_rest:
view:
mime_types:
json:
- 'application/json'
- 'application/json;version=1.0'
- 'application/json;version=1.1'
format_listener:
media_type:
version_regex: '/(v|version)=(?P<version>[0-9\.]+)/'
```
```
Accept: application/vnd.my_entity;version=1.1
```
```
class Person
{
/** @Until("1.0") */
private $name;
/** @Since("1.1") */
private $lastname;
}
```
</script>
</section>
<section data-markdown>
<script type="text/template">
## Message Decoding
* Listener to decode message body from XML, JSON etc. into the "request" parameter bag
* Integration with SensioFrameworkExtraBundle converters to turn parameters to objects
* GET parameter validation and normalization
```
PUT /users/1 HTTP/1.1
Host: example.org
Accept: application/json;q=0.9,*/*;q=0.8
Content-Type: application/json
{"name":"Don Johnson"}
```
```
public functon putAction(Request $request)
{
$request->request('name');
}
```
</script>
</section>
<section data-markdown>
<script type="text/template">
## Allowed Methods Listener
* Examines all available routes to determine what HTTP methods are available for the request URI
* Automatically sets an according ALLOW header in the response
```
fos_rest:
allowed_methods_listener: true
```
```
HTTP/1.1 200 OK
Allow: GET, POST
```
</script>
</section>
<section data-markdown>
<script type="text/template">
## Error Handling
* Return correct HTTP status code
* Determine for which exception to expose the exception message
* Automatically extract errors from a Form instance
```
fos_rest:
exception:
codes:
'Symfony\Component\Routing\Exception\ResourceNotFoundException': 404
'Doctrine\ORM\OptimisticLockException': HTTP_CONFLICT
messages:
'Symfony\Component\Routing\Exception\ResourceNotFoundException': true
```
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
## BazingaHateoasBundle
</script>
</section>
<section data-markdown>
<script type="text/template">
## BazingaHateoasBundle
* Integrates the Hateoas library with Symfony2
* Leverages the JMS Serializer library
* Relies on the Symfony2 **ExpressionLanguage** component
* Supports JSON and XML
* Allows to configure **links** and **embedded resources** in<br>XML, YAML, PHP, or Annotations
* Dynamic relations (relation providers)
* Exclusion strategies
</script>
</section>
<section data-markdown>
<script type="text/template">
## Usage
```
use JMS\Serializer\Annotation as Serializer;
use Hateoas\Configuration\Annotation as Hateoas;
/**
* @Serializer\XmlRoot("user")
*
* @Hateoas\Relation("self", href = "expr('/api/users/' ~ object.getId())")
*/
class User
{
/** @Serializer\XmlAttribute */
private $id;
private $firstName;
private $lastName;
public function getId() {}
}
```
</script>
</section>
<section data-markdown>
<script type="text/template">
## JSON
```
$hateoas = HateoasBuilder::create()->build();
$json = $hateoas->serialize(new User(123, 'John', 'Doe'), 'json');
```
```
{
"id": 123,
"first_name": "John",
"last_name": "Doe",
"_links": {
"self": {
"href": "/api/users/123"
}
}
}
```
</script>
</section>
<section data-markdown>
<script type="text/template">
## XML
```
$hateoas = HateoasBuilder::create()->build();
$xml = $hateoas->serialize(new User(123, 'John', 'Doe'), 'xml');
```
```
<user id="123">
<first_name><![CDATA[John]]></first_name>
<last_name><![CDATA[Doe]]></last_name>
<link rel="self" href="/api/users/123"/>
</user>
```
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
## TemplatedUriBundle
</script>
</section>
<section data-markdown>
<script type="text/template">
## RFC 6570: URI Template
A compact sequence of characters for describing a range of URIs through variable expansion.
<br>
<table>
<thead>
<tr>
<th>URIs</th>
<th>URI Template</th>
</tr>
</thead>
<tbody>
<tr>
<td><a href="http://example.com/~fred/">http://example.com/~fred/</a></td>
<td rowspan="2"><a href="http://example.com/~{username}/">http://example.com/~{username}/</a></td>
</tr>
<tr>
<td><a href="http://example.com/~mark/">http://example.com/~mark/</a></td>
</tr>
</tbody>
</table>
</script>
</section>
<section data-markdown>
<script type="text/template">
## Usage
```
demo_route:
pattern: /demo/{page}
```
```
$templateLink = $this
->get('hautelook.router.template')
->generate('demo_route', array(
'page' => '{page}',
'sort' => '{sort}',
'filter' => array('{filter}'),
));
```
```
/demo/{page}?{&sort}{&filter%5B%5D*}
```
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
## NelmioApiDocBundle
</script>
</section>
<section data-markdown>
<script type="text/template">
## In A Nutshell
* Generates documentation for your REST APIs
* Gathers information from PHPDoc
* Supports FOSRestBundle, SensioFrameworkExtraBundle, JMSSerializerBundle
and JMSSecurityExtraBundle annotations
* Supports **your own annotations**
* Allows to add **your own parsers**
* Sandbox (**Killer Feature!**)
</script>
</section>
<section data-markdown>
<script type="text/template">
## Usage
```
/**
* List all notes.
*
* @ApiDoc(
* resource = true,
* statusCodes = { 200 = "Returned when successful" }
* )
* @QueryParam(
* name="offset", requirements="\d+", nullable=true,
* description="Offset from which to start listing notes."
* )
* @QueryParam(
* name="limit", requirements="\d+", default="5",
* description="How many notes to return."
* )
*/
public function getNotesAction() {}
```
</script>
</section>
<section>
<img src="images/sfcon2k13/apidocbundle.png" class="no-border" />
</section>
</section>
<section data-markdown>
<script type="text/template">
## FOSHttpCacheBundle
* Set path-based cache expiration headers via app confign
* Set up an invalidation scheme without writing PHP code
* Tag your responses and invalidate cache based on tags
* Send invalidation requests with minimal performance impact (Varnish and Nginx supported out of the box)
* Differentiate caches based on user type (e.g. roles)
* Easily implement HTTP cache client
</script>
</section>
<section>
<section data-markdown>
<script type="text/template">
## OAuth
</script>
</section>
<section data-markdown>
<script type="text/template">
OAuth is an **open protocol** to allow **secure authorization**<br>in a simple and
**standard method** from web, mobile<br>and desktop applications.
<br>
It is an **authorization framework** that enables a third-party application to
**obtain limited access to an HTTP service**.
<p>
<br><br>
<small>
[http://edu.williamdurand.fr/security-slides/#slide85](http://edu.williamdurand.fr/security-slides/#slide85)
</small>
</p>
</script>
</section>
<section data-markdown>
<script type="text/template">
## HWIOAuthBundle
* Client-side implementation
* Support 20+ different providers
* Supports both OAuth1.0a and OAuth2
</script>
</section>
<section data-markdown>
<script type="text/template">
## FOSOAuthServerBundle
* Server-side implementation of OAuth2
* Supports Doctrine ORM|ODM, Propel
* Highly configurable
<br>
Thank you [Alan Gabriel Bem](https://github.com/alanbem) for helping us!
<br>
[BazingaOAuthServerBundle](https://github.com/willdurand/BazingaOAuthServerBundle) for OAuth1.0a.
</script>
</section>
</section>
<section data-markdown>
<script type="text/template">
## Thank You.
### Questions?
</script>
</section>
<section data-markdown>
<script type="text/templte">
## Further Reading
* http://martinfowler.com/articles/richardsonMaturityModel.html
* http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven
* http://www.slideshare.net/Wombert/designing-http-interfaces-and-restful-web-services-dpc2012-20120608
* http://williamdurand.fr/2012/08/02/rest-apis-with-symfony2-the-right-way/
* http://www.mnot.net/blog/2012/12/04/api-evolution
* http://knpuniversity.com/blog/what-the-rest
* http://knpuniversity.com/blog/rest-revisited
</script>
</section>
</div>
</div>
<script type="text/javascript" src="js/sfcon2k13/head.min.js"></script>
<script type="text/javascript" src="js/sfcon2k13/reveal.min.js"></script>
<script type="text/javascript">
Reveal.initialize({
controls: true,
progress: true,
history: true,
center: true,
theme: Reveal.getQueryHash().theme,
transition: Reveal.getQueryHash().transition || 'concave',
// Optional libraries used to extend on reveal.js
dependencies: [
{ src: 'js/sfcon2k13/classList.js', condition: function() { return !document.body.classList; } },
{ src: 'js/sfcon2k13/marked.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'js/sfcon2k13/markdown.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'js/sfcon2k13/highlight.js', async: true, callback: function() { hljs.initHighlightingOnLoad(); } },
{ src: 'js/sfcon2k13/pageNumbers.js' },
]
});
</script>
</body>
</html>