-
Notifications
You must be signed in to change notification settings - Fork 4
/
Copy pathrest-dans-le-monde-symfony.html
1025 lines (884 loc) · 46.8 KB
/
rest-dans-le-monde-symfony.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
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html>
<head>
<title>REST dans le monde Symfony | William Durand @ Bdx.io</title>
<link rel="stylesheet" href="css/sfcon2k13/reveal.min.css">
<link rel="stylesheet" href="css/bdxio/theme.css" id="theme">
<link rel="stylesheet" href="css/sfcon2k13/zenburn.css">
<link rel="stylesheet" href="css/sfcon2k13/pageNumbers.css">
<link rel="stylesheet" href="font-awesome/css/font-awesome.min.css">
<link rel="stylesheet" href="css/fix-fontawesome-reveal-js.css">
<link rel="stylesheet" href="css/bdxio/custom.css">
<script>
if (window.location.search.match(/print-pdf/gi)) {
document.write('<link rel="stylesheet" href="css/sfcon2k13/pdf.css" type="text/css">');
}
</script>
</head>
<body>
<img src="images/bdxio/logo-bdxio.png" class="bdxio-logo" />
<div class="reveal">
<div class="slides">
<section>
<h1 class="title">REST dans le<br>monde Symfony</h1>
<em>William Durand - October 17th, 2014</em>
</section>
<section>
<section data-markdown>
<script type="text/template">
## Introduction to REST
</script>
</section>
<section data-markdown>
<script type="text/template">
### **RE**presentational **S**tate **T**ransfer
REST is the underlying architectural principle of the web.
It is formalized as a set of **constraints**,
described in<br>**Roy Fielding**'s dissertation.
</script>
</section>
<section data-markdown>
<script type="text/template">
### **R**ichardson **M**aturity **M**odel
<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">
### Level 0 - The Swamp of POX
* HTTP as a tunneling mechanism
* RPC style system (SOAP, XML-RPC)
<br>
</script>
</section>
<section data-markdown>
<script type="text/template">
### Level 1 - Resources
* Individual resources (**URI**s)
* Notion of object identity
<br>
</script>
</section>
<section data-markdown>
<script type="text/template">
### Level 2 - HTTP Verbs
* **Client** uses specific HTTP **verbs**
* **Server** uses HTTP **status codes**
<br>
</script>
</section>
<section data-markdown>
<script type="text/template">
### HTTP Verbs
<p /><center>
| Method | Safe? | Idempotent? |
|:--------:|:-----:|:-----------:|
| `GET` | yes | yes |
| `HEAD` | yes | yes |
| `POST` | no | no |
| `PUT` | no | yes |
| `DELETE` | no | yes (*) |
| ... | no | no |
</center>
**Safe**: means cacheable.
**Idempotent**: result independent<br>on the number of executions.
</script>
</section>
<section data-markdown>
<script type="text/template">
### HTTP Status Codes
<p /><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 data-markdown>
<script type="text/template">
### Level 3 - Hypermedia Controls
* Service discovery via link relations
* Hypermedia formats (ATOM, HAL, JSON-LD, etc.)
<br>
</script>
</section>
<section data-markdown>
<script type="text/template">
### Level 3
### =
### Content Type Negotiation
### +
### HATEOAS
</script>
</section>
<section data-markdown>
<script type="text/template">
### Content Type Negotiation
Content Type Negotiation is the principle of **finding appropriate response
formats** based on client requirements.
<br>
* **No standardized algorithm available**
* Apache [mod_negotiation](http://httpd.apache.org/docs/2.4/content-negotiation.html) algorithm is documented though
* 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>
<section data-markdown>
<script type="text/template">
### HATEOAS
**H**ypermedia **A**s **T**he **E**ngine **O**f
**A**pplication **S**tate.
It means that hypermedia should be used to find your
<br>way through the API. It is all about **state
transitions**.
Your application is just a big **state machine**.
```
<?xml version="1.0" encoding="UTF-8"?>
<collection page="1" limit="10" pages="1">
<user id="123"></user>
<user id="456"></user>
<link rel="self" href="/api/users?page=1&limit=10" />
<link rel="first" href="/api/users?page=1&limit=10" />
<link rel="last" href="/api/users?page=1&limit=10" />
</collection>
```
</script>
</section>
<section data-markdown>
<script type="text/template">
### So much for the REST theory ...
</script>
</section>
<section data-markdown>
<script type="text/template">
### Let's Meet the PHP World!
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
In order to comply with RMM Level 1,<br>I want to turn business objects/data to **resources**.
</script>
</section>
<section data-markdown>
<script type="text/template">
## JMS Serializer
<br>
<i class="fa fa-github"></i> [schmittjoh/serializer](https://github.com/schmittjoh/serializer)
</script>
</section>
<section data-markdown>
<script type="text/template">
### In A Nutshell
* 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
* Quite easy to extend
</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>
<p>In order to comply with RMM Level 2,<br>I want to use proper <strong>HTTP verbs</strong> and <strong>status codes</strong>.</p>
</section>
<section>
<p>But I need to understand what the client wants and says.</p>
<p class="fragment">And I also need to rely on a serializer.</p>
<p class="fragment">And I will have to deal with filters, versioning, etc.</p>
<p class="fragment"><br><strong>I need a framework!</strong></p>
</section>
<section data-markdown>
<script type="text/template">
## FOSRestBundle (+ Symfony)
<br>
<i class="fa fa-github"></i> [FriendsOfSymfony/FOSRestBundle](https://github.com/FriendsOfSymfony/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, and JSON from a single action
* Automatic generation of routes from actions
* GET parameter parsing and validation
* Integration with Symfony serializer and JMS Serializer
* Accept header negotiation (thx to the [Negotiation](https://github.com/willdurand/Negotiation) lib)
* Request body decoding
* API versioning
</script>
</section>
<section data-markdown>
<script type="text/template">
### Usage
```
class RestController
{
/**
* 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)
{
//$page = $request->query->get('page');
//$page = preg_match('\d+', $page) ? $page : 1;
$articles = [ '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">
### Content Type Negotiation
fos_rest:
format_listener:
rules:
-
path: ^/
priorities: [ html, json, xml ]
fallback_format: ~
prefer_extension: true
<p />
Accept: application/json, application/xml;q=0.9, text/html;q=0.8,
text/*;q=0.7, */*;q=0.5
<i class="fa fa-github"></i> [willdurand/Negotiation](https://github.com/willdurand/Negotiation)
</script>
</section>
<section data-markdown>
<script type="text/template">
## Version Listener
```
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/json;version=1.1
```
```
class User
{
/** @Until("1.0") */
private $name;
/** @Since("1.1") */
private $lastname;
}
```
</script>
</section>
<section data-markdown>
<script type="text/template">
### Message Decoding
* Decode request body from XML, JSON, etc. into the `request`
* Integration with converters to turn parameters to objects
* GET parameter validation and normalization
```
POST /users HTTP/1.1
Accept: application/json,*/*;q=0.8
Content-Type: application/json
{"name":"Don Johnson"}
```
```
public functon postAction(Request $request)
{
$name = $request->request->get('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
<br>
fos_rest:
allowed_methods_listener: true
```
HTTP/1.1 200 OK
Allow: GET, POST
```
</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
<br>
fos_rest:
view:
mime_types:
json: ['application/json', 'application/vnd.example-com.foo+json']
rss: 'application/rss+xml'
jpg: 'image/jpeg'
png: 'image/png'
jsonp_handler: ~
<br>
<i class="fa fa-info-circle"></i> JSONP callback validation thanks to the
<br>[willdurand/JsonpCallbackValidator](https://github.com/willdurand/JsonpCallbackValidator) library
</script>
</section>
<section data-markdown>
<script type="text/template">
### Error/Exception Handling
* Return correct HTTP status code
* Determine for which exception to expose the exception message
* Automatically extract errors from a `Form` instance
<br>
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 data-markdown>
<script type="text/template">
## Want A Smarter Mapping?
<br>
<i class="fa fa-github"></i> [TheBigBrainsCompany/rest-util](https://github.com/TheBigBrainsCompany/rest-util)
</script>
</section>
<section data-markdown>
<script type="text/template">
### Usage
```
$invalidArgumentExceptionMapping = new ExceptionMapping(array(
'exceptionClassName' => '\InvalidArgumentException',
'factory' => 'default',
'httpStatusCode' => 400,
'errorCode' => 400101,
'errorMessage' => null,
'errorExtendedMessage' => 'Extended message',
'errorMoreInfoUrl' => 'http://api.my.tld/doc/error/400101',
));
$exceptionMap = new ExceptionMap();
$exceptionMap->add($invalidArgumentExceptionMapping);
$errorResolver = new ErrorResolver($exceptionMap);
$error = $errorResolver->resolve(
new \InvalidArgumentException('This is an invalid argument exception.')
);
```
</script>
</section>
<section data-markdown>
<script type="text/template">
### Symfony Bundle Configuration
```
tbbc_rest_util:
error:
exception_mapping:
InvalidArgumentException:
class: "InvalidArgumentException"
factory: default
http_status_code: 400
error_code: 400101
error_message: ~
extended_message: "Extended message"
more_info_url: "http://api.my.tld/doc/error/400101"
```
</script>
</section>
<section data-markdown>
<script type="text/template">
### Example
```
print_r($error->toArray());
```
```
Array
(
[http_status_code] => 400
[code] => 400101
[message] => This is an invalid argument exception.
[extended_message] => Extended message
[more_info_url] => http://api.my.tld/doc/error/400101
)
```
```
echo json_encode($error->toArray());
```
```
{
"http_status_code": 400,
"code": 400101,
"message": "This is an invalid argument exception.",
"extended_message": "Extended message",
"more_info_url": "http:\/\/api.my.tld\/doc\/error\/400101"
}
```
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
In order to comply with RMM Level 3,<br>I want to **HATEOAS** ALL THE THINGS!
</script>
</section>
<section data-markdown>
<script type="text/template">
## Hateoas
<br>
<i class="fa fa-github"></i> [willdurand/Hateoas](https://github.com/willdurand/Hateoas)
</script>
</section>
<section data-markdown>
<script type="text/template">
### In A Nutshell
* 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');
<br>
{
"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');
<br>
<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>
<section data-markdown>
<script type="text/template">
In order to make my API more <strike>fancy</strike> self-documenting,<br>I want to use **URI Templates**.
</script>
</section>
<section data-markdown>
<script type="text/template">
### RFC 6570: URI Template
A compact sequence of characters for describing<br>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">
## TemplatedUriRouter
<br>
<i class="fa fa-github"></i> [hautelook/TemplatedUriRouter](https://github.com/hautelook/TemplatedUriRouter)
</script>
</section>
<section data-markdown>
<script type="text/template">
### Usage
demo_route:
pattern: /demo/{page}
<p />
$templateLink = (new Rfc6570Generator($routes))
->generate('demo_route', array(
'page' => '{page}',
'sort' => '{sort}',
'filter' => array('{filter}'),
));
<br>
/demo/{page}?{&sort}{&filter%5B%5D*}
<br>
<i class="fa fa-info-circle"></i> Leverages the [Symfony Routing component](http://symfony.com/doc/current/components/routing/introduction.html).
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
In order to [make humans happy|dominate the world|whatever],
<br>I want to create **documentation** for my API.
</script>
</section>
<section data-markdown>
<script type="text/template">
## Swagger UI
<br>
<i class="fa fa-github"></i> [wordnik/swagger-ui](https://github.com/wordnik/swagger-ui)
</script>
</section>
<section data-markdown>
<script type="text/template">
## NelmioApiDocBundle
<br>
<i class="fa fa-github"></i> [nelmio/NelmioApiDocBundle](https://github.com/nelmio/NelmioApiDocBundle)
</script>
</section>
<section data-markdown>
<script type="text/template">
### In A Nutshell
* Designed for Symfony
* Generates documentation for your REST APIs
* Gathers information from PHPDoc
* Supports FOSRestBundle, SensioFrameworkExtraBundle, JMSSerializerBundle
and JMSSecurityExtraBundle
* Supports **your own annotations** and **you own parsers**
* Sandbox (**Killer Feature ♥**)
* Swagger compliant
</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 data-markdown>
<script type="text/template">
## ng-admin
<br>
<i class="fa fa-github"></i> [marmelab/ng-admin](https://github.com/marmelab/ng-admin)
</script>
</section>
<section>
<img src="images/bdxio/ng-admin.png" class="no-border" />
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
In order to not burn too many servers,<br>I want to add and manage a **caching layer**.
</script>
</section>
<section data-markdown>
<script type="text/template">
## FOSHttpCache
<br>
<i class="fa fa-github"></i> [FriendsOfSymfony/FOSHttpCache](https://github.com/FriendsOfSymfony/FOSHttpCache)
</script>
</section>
<section data-markdown>
<script type="text/template">
### In A Nutshell
* Set path-based cache expiration headers via app config
* 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>
<section data-markdown>
<script type="text/template">
## Demo?
</script>
</section>
<section data-markdown>
<script type="text/template">
### <i class="fa fa-github"></i> [willdurand/Propilex](https://github.com/willdurand/Propilex)
</script>
</section>
<section data-markdown>
<script type="text/template">
### <i class="fa fa-github"></i> [gimler/symfony-rest-edition](https://github.com/gimler/symfony-rest-edition)
</script>
</section>
</section>
<section data-markdown>
<script type="text/template">
## Thank You.
### Questions?
<br>
<br>
<br>
<ul class="me">
<!--
<li>
<p><i class="fa fa-comments-o"></i><a href="https://joind.in/11215" title="joindin">joind.in/11215</a></p>
</li>
-->
<li>
<p><i class="fa fa-globe"></i><a href="http://williamdurand.fr" title="website">williamdurand.fr</a></p>
</li>
<li>
<p><i class="fa fa-github"></i><a href="https://github/willdurand" title="github">github.com/willdurand</a></p>
</li>
<li>
<p><i class="fa fa-twitter"></i><a href="https://twitter.com/couac" title="twitter">twitter.com/couac</a></p>
</li>
</ul>
</script>
</section>
<section data-markdown>
<script type="text/template">
<p>
<small>
[https://knpuniversity.com/screencast/rest](https://knpuniversity.com/screencast/rest)
</small>
</p>
</script>
</section>
<section data-markdown>
<script type="text/templte">
## Further Reading
<small>
* http://www.ietf.org/rfc/rfc2616.txt
* 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
* http://timelessrepo.com/haters-gonna-hateoas
* http://blog.liip.ch/archive/2013/10/28/resting-with-symfony2.html
* http://williamdurand.fr/2014/02/14/please-do-not-patch-like-an-idiot/
</small>
</script>
</section>
<section>
<section data-markdown>
<script type="text/template">
## OAuth
</script>
</section>
<section data-markdown>
<script type="text/template">
### What Is OAuth?
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
<br>
<i class="fa fa-github"></i> [hwi/HWIOAuthBundle](https://github.com/hwi/HWIOAuthBundle)
</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>
<i class="fa fa-github"></i> [FriendsOfSymfony/FOSOAuthServerBundle](https://github.com/FriendsOfSymfony/FOSOAuthServerBundle)
<br>
<i class="fa fa-github"></i> [willdurand/BazingaOAuthServerBundle](https://github.com/willdurand/BazingaOAuthServerBundle) (OAuth1.0a)
</script>
</section>
</section>
</div>