2. Content:
• Introduction to Web Services.
• Saying Hi to the Services module.
• More about Services. Expanding the module.
• Working example.
• Creating our own resources.
• Round-up.
www.wearepropeople.com
3. Introduction to Web
Services:
• XML-RPC / SOAP based Services
• JavaScript Services
• RESTful Services
• Other (details in other sessions)
www.wearepropeople.com
4. Why do we need Services?
www.wearepropeople.com
5. Why do we need Services?
www.wearepropeople.com
6. Why do we need Services?
www.wearepropeople.com
7. Why do we need Services?
www.wearepropeople.com
10. XML-RPC:
XML-RPC is a remote procedure call
(RPC) protocol which uses XML to encode
its calls and HTTP as a transport
mechanism. "XML-RPC" also refers
generically to the use of XML for remote
procedure call, independently of the specific
protocol.
www.wearepropeople.com
13. In result our API might look like:
www.wearepropeople.com
14. SOAP:
SOAP, originally defined as Simple Object Access
Protocol, is a protocol specification for exchanging
structured information in the implementation of
Web Services in computer networks. It relies on
Extensible Markup Language (XML) for its message format,
and usually relies on other Application Layer protocols, most
notably Hypertext Transfer Protocol(HTTP) and
Simple Mail Transfer Protocol (SMTP), for message
negotiation and transmission.
www.wearepropeople.com
18. REST / RESTful APIs
REpresentational State Transfer (REST) is a style of
software architecture for distributed systems such as the
World Wide Web. REST has emerged over the past few years as
a predominant Web service design model. REST has increasingly
displaced other design models such as SOAP and WSDL due to
its simpler style.
www.wearepropeople.com
22. Hello Services Module!
uc Use Case Model
Requestor Requestor
Request
Request
EndPoint
API
Resource Node
Resource Whatev er
Resource User
www.wearepropeople.com
