SLIDE 1
Take a small REST
Simple approaches for REST in smalltalk Norbert Hartl 2denker
What we do...
...at 2denker mobile applications backend services for mobile applications backend services for b2b
Take a small REST Simple approaches for REST in smalltalk Norbert - - PowerPoint PPT Presentation
Take a small REST Simple approaches for REST in smalltalk Norbert - - PowerPoint PPT Presentation
Take a small REST Simple approaches for REST in smalltalk Norbert Hartl 2denker What we do... ...at 2denker mobile applications backend services for mobile applications backend services for b2b Why REST? there are RPC-style services (SOAP
SLIDE 2
SLIDE 3
Why REST?
there are RPC-style services (SOAP , XML-RPC,...)
SLIDE 4
Why REST?
there are RPC-style services (SOAP , XML-RPC,...) REST is data-centric
SLIDE 5
Why REST?
there are RPC-style services (SOAP , XML-RPC,...) REST is data-centric REST/HTTP has meta data
SLIDE 6
Why REST?
there are RPC-style services (SOAP , XML-RPC,...) REST is data-centric REST/HTTP has meta data REST is about identity
SLIDE 7
Smalltalk tools to do REST
Magritte Magritte-XMLBinding Magritte-JSON Seaside-REST
SLIDE 8
serialization/materialization
using magritte meta tool support model with meta information validation of model using meta information conversion into/from formats with meta info
SLIDE 9
Example class Person
fullName emailAddress
SLIDE 10
model with meta information
Person>>#fullNameDescription <magritteDescription> ^ MAStringDescription new accessor: #fullName; label: 'full name'; beRequired; priority: 100; yourself
SLIDE 11
model with meta information
(using pragma to add a description)
Person>>#fullNameDescription <magritteDescription> ^ MAStringDescription new accessor: #fullName; label: 'full name'; beRequired; priority: 100; yourself
SLIDE 12
model with meta information
(adding type information)
Person>>#fullNameDescription <magritteDescription> ^ MAStringDescription new accessor: #fullName; label: 'full name'; beRequired; priority: 100; yourself
SLIDE 13
model with meta information
(specifying value store/retrieve operation)
Person>>#fullNameDescription <magritteDescription> ^ MAStringDescription new accessor: #fullName; label: 'full name'; beRequired; priority: 100; yourself
SLIDE 14
validation using meta info
(magritte)
Person>>#emailAddressDescription <magritteDescription> ^ MAStringDescription new accessor: #emailAddress; label: 'email address'; addCondition: [:val| val includes: $@ ] labelled: 'address must contain @'; beRequired; priority: 200; yourself
SLIDE 15
validation using meta info
(magritte)
Person>>#emailAddressDescription <magritteDescription> ^ MAStringDescription new accessor: #emailAddress; label: 'email address'; addCondition: [:val| val includes: $@ ] labelled: 'address must contain @'; beRequired; priority: 200; yourself
SLIDE 16
validation using meta info
(magritte)
Person>>#emailAddressDescription <magritteDescription> ^ MAStringDescription new accessor: #emailAddress; label: 'email address'; addCondition: [:val| val includes: $@ ] labelled: 'address must contain @'; beRequired; priority: 200; yourself
SLIDE 17
adding conversion info
(for Magritte-XMLBinding)
fullNameXmlDescription: aDescription <magritteDescription: #fullNameDescription> ^ aDescription xmlElementName: 'fullname' emailAddressXmlDescription: aDescription <magritteDescription: #emailAddressDescription> ^ aDescription xmlAttributeName: 'email'
SLIDE 18
conversion into/from format
p := Person new. p fullName: 'John Doe'; emailAddress: 'john@doe.it'. p magritteDescription toXml: p
<Person email="john@doe.it"> <fullname>John Doe</fullname> </Person>
SLIDE 19
REST call flow
message routing and parameter handling content type selection serializiation/materialization to/from network data
SLIDE 20
message routing
time <get> <path: '/time'> self requestContext response status: 200; nextPutAll: Time now greaseString; respond
SLIDE 21
message routing
(matching HTTP verb)
time <get> <path: '/time'> self requestContext response status: 200; nextPutAll: Time now greaseString; respond
SLIDE 22
message routing
(matching path/parameters)
time <get> <path: '/time'> self requestContext response status: 200; nextPutAll: Time now greaseString; respond
SLIDE 23
content type xml
getPersonXml: aString <get> <path: '/person/{1}'> <produces: 'application/xml'> self requestContext response status: 200; nextPutAll: ( self description toXml: (self personWithId: aString)); respond
SLIDE 24
content type xml
(placeholder in url become method paramter)
getPersonXml: aString <get> <path: '/person/{1}'> <produces: 'application/xml'> self requestContext response status: 200; nextPutAll: ( self description toXml: (self personWithId: aString)); respond
SLIDE 25
content type xml
(content type selection based on Accept header)
getPersonXml: aString <get> <path: '/person/{1}'> <produces: 'application/xml'> self requestContext response status: 200; nextPutAll: ( self description toXml: (self personWithId: aString)); respond
SLIDE 26
content type json
getPersonJson: aString <get> <path: '/person/{1}'> <produces: 'application/json'> self requestContext response status: 200; nextPutAll: (String streamContents: [:stream| (self personWithId: aString) jsonOn: stream]); respond
SLIDE 27
example post
addPersonFromJson <post> <path: '/person'> <consumes: 'application/json'> self addPersonUsing: [ self materializeFromJson ]
SLIDE 28
example post
(content type selection based on Content-Type header)
addPersonFromJson <post> <path: '/person'> <consumes: 'application/json'> self addPersonUsing: [ self materializeFromJson ]
SLIDE 29
Demo
SLIDE 30