Mobile Web Services (PDF)

Chapter 1: Introduction. 1.1 Structure of this Book. Chapter 2: Introduction to XML. 2.1 Markup and Elements. 2.2 Attributes. 2.3 XML Declaration. 2.4 Namespaces. 2.5 Well-Formedness and Validity. 2.6 XML Schema. 2.7 Summary. Chapter 3: Introduction to Service-Oriented Architectures. 3.1 Service-Oriented Architecture. 3.2 Web Services Messaging. 3.3 Web Service Description. 3.4 Web Service Discovery. 3.5 Summary. Chapter 4: Agreement. 4.1 Web Services Addressing. 4.2 Background. 4.3 Purpose of WS-Addressing. 4.4 Mobile Application Example. 4.5 WS-Addressing Core. 4.6 Binding Specifications. 4.7 Conclusions. 4.8 Policy. Chapter 5: Identity and Security. 5.1 Identity and Web Services. 5.2 Security and Web Services. 5.3 Summary. Chapter 6: Liberty Alliance Identity Technologies. 6.1 Liberty Identity Federation Framework (ID-FF). 6.2 Liberty Identity Web Service Framework (ID-WSF). 6.3 Liberty Identity Service Interface Specifications (ID-SIS). 6.4 Summary. Chapter 7: Enabling Mobile Web Services. 7.1 Mobile Web Services Software Development Environment. 7.2 SOA for S60 Platform Architecture. 7.3 A Simple Example. 7.4 Identity Web Services Support. 7.5 Web Service Providers. 7.6 SOA for S60 Platform as a Pluggable Architecture. 7.7 SOA for S60 Platform XML Processing. 7.8 Writing Code for Web Service Consumer Applications. 7.9 Summary. Chapter 8: Summary and Next Steps. Chapter 9: Java Client Development. 9.1 Prerequisites. 9.2 Nokia Web Services Framework for Java Architecture. 9.3 XML Processing in NWSF. 9.4 HelloWS Example. 9.5 Connecting to Web Services. 9.6 Using the Service Database. 9.7 Identity and Security. 9.8 HelloWS.java. 9.9 AddressBook Example. Chapter 10: C++ Client Development. 10.1 Nokia Service Development API. 10.2 Hello Web Service Example. 10.3 NWSF Service Connection Library. 10.4 Sending Messages to a Web Service. 10.5 NWSF Service Manager Library. 10.6 NWSF Service Description Library. 10.7 NWSF and Identity. 10.8 Policy and Services. 10.9

Frederick Hirsch, a Senior Architect at Nokia, is
responsible for the company's Web Services standardization
strategy, and for security in Web service products. He is an active
contributor to the Web Services Security and Digital Signature
Services committees of OASIS, and has worked as an editor in the
OASIS Security Services technical committee (SAML 2.0). Frederick
is also an editor of the Security Mechanisms specifications in the
Technical Expert Group of the Liberty Alliance, and has contributed
security sections to the Mobile Web Services architecture and
specification of the Open Mobile Alliance. He has also participated
in the XML Signature and XML Encryption working groups of W3C, and
has co-edited the W3C XKMS requirements. He is Nokia's
primary voting representative at OASIS and WS-I, and a member of
the OASIS Board of Directors, where he chairs the Strategy
Committee. He has extensive experience in distributed systems and
security, having worked at AT&T Bell Laboratories, BBN, Open
Software Foundation (OSF; later the Open Group Research Institute),
and CertCo, as well as a number of smaller companies. He holds
degrees from MIT, Stanford, and Boston University.

John Kemp has spent the past two years intimately
involved in the development of the Nokia Web services architecture.
During that time, he has edited and contributed to several Web
service specifications, including the Liberty Alliance Identity
Federation and Identity Web Services frameworks, and the OASIS
Security Services SAML 2 specification. John has been involved in
developing Internet-scale software systems since 1996, helping to
build one of the first Web browser-based software
applications, the Employease Network. Prior to joining Nokia, John
was an independent software developer whose clients included
Deutsche Bank and the Liberty Alliance. He holds a degree in
Computer Science and Artificial Intelligence, and is now learning
to play the ukulele.

Norbert

Dieses eBook können Sie uneingeschränkt auf allen Geräten der tolino Familie lesen. Zum Lesen auf sonstigen eReadern und am PC benötigen Sie eine Adobe ID.