|
|
Therapist Directory: Find a Psychologist, Find a Therapist, Find a Marriage Counselor
PSYCHOLOGY TOPICS
Selected topics in psychology
and mental health.
|
|
|
|
|
THE THERAPIST PSYCHOLOGIST BOOK STORE
 | |
 View Larger |
Web Services Platform Architecture: SOAP, WSDL, WS-Policy, WS-Addressing, WS-BPEL, WS-Reliable Messaging, and More By Sanjiva WeerawaranaFrancisco CurberaFrank LeymannTony StoreyDonald F. Ferguson ( Prentice Hall PTR )
Release Date: 2005-04-01
Average Customer Rating:
List Price: $54.99
Price: $34.64
Eligible for FREE Super Saver Shipping on orders over $25.
Availability: Usually ships in 24 hours
|  Add to Cart |
|
|
|
Great Theortical Reference to the WS-* Stack ( mahesh9999 )
This is a great reference book for the Web Services Stack and all the new specification and how they all fit in. Good starter when looking for a solution, but you will need other references for implementation.
|
Very good conceptual and technical introduction to the Web Services like SOA components ( fxmarin )
This book is specially interesting by its chapter of introduction to the BPEL, since it is a subject that does not treat in almost any book of technical form.
It is a very interesting book so that it introduces to the reader in all the concepts and technologies involved in the Web Services focusing it towards a services oriented architecture.
It does not get to be a complete book on SOA, tries it either, but it provides good bases.
What makes very interesting to the book is that each concept and architecture introduce it very correctly and later makes one more an approach more technical, with examples of code, or definitions.
Everything and not to be a complete guide if who provides a very ample vision and detailed enough, so that the reader concretely knows that he is being spoken at every moment and he knows by where must extend its knowledge.
He lays the way to the knowledge of the technologies implied in the Web Services.
A very special chapter is of the BPEL where aside from introducing conceptually it gives it a good technical introduction providing to the reader the technical foundations to know the BPEL and power to confront a following deeper learning of the matter of more comfortable form.
It provides the necessary keys and concepts, as well as a general vision, allowing a later learning of the matters that interest easily but.
It is a book that nowadays is updated with the technologies that treatment.
Recommended for a very good conceptual and technical introduction to the Web Services, of form independently and like tool of SOA.
|
 Not a bad book - Good fundamentals less on development focus ( paullopez5 )
This book is all about Web services platform architecture and standards. It cooks well on most of the alphabet soup of web services standards. This book would guide you instead of browsing over the internet for what is what. The book falls short on guidelines for implementing them. The book also a bit old in its evolving specifications and endorsed standards coverage particularly less about WS-I and WS-Security* standards. That is disappointing.
|
Explains all you need to know about the Web Services Platform ( sediga )
What do you get when you put a number of Web Services gurus from IBM in a room for a while? You'll get the "Web Services Platform Architecture" book. In short, all the authors that assisted in writing this book are Web services experts from IBM who have either wrote the specs or assisted in writing the Web services specs in question. The nice thing about the book is that is it an easy read. It is not a dry, boring, "reading-these-specs is-putting-my-to-sleep," book. As you know, there are a number of specs that cover Web services, so the authors have a taken a short-and-sweet approach to each protocol. Each protocol is covered in detail, but the detail surrounds why you would want to care about this protocol, and not what paragraph 4, subparagraph 8 of chapter 2 of WS-Security says about naming conventions, for example. Each chapter ties the business needs to the technical aspects of the protocol, and talks about how the protocol can be used to solve a given business problem.
The following protocols are covered in this text:
Messaging-type protocols such as WS-Addressing
Description-type protocols such as WS-Policy, and WSDL
Protocols that are used for QoS specification such as WS-Security, WS-Reliable Messaging, WS-Atomic Transaction and WS-Business Activity
Security type protocols (WS-Security) and other related protocols such as WS-Trust, WS-Privacy, WS-Federation and WS-Authorization
Workflow and composition type protocols such as WS-BPEL.
As the authors move "up" the stack (the protocols are presented and classified very similar to what I described above - layers atop of the transport protocols such as TCP/HTTP), the business examples get more and more involved and complicated. You need to realize that there is not much code writing actually occurs in this book, but a high-level architectural methodology of how different pieces of the Wed services stack fit together, and compliment each other. The different examples given demonstrate another very crucial fact: an architect can pick and choose the protocol and standard s/he wants to get the job done. Web services protocols are by no means an all-or-nothing concept. This is why interoperability of various protocols very important, and the main reason why some of these protocols are stuck at the "final" stages of approval committee for such a long time.
Two case studies are presented at the end of the text that covers the end-to-end model of the protocols. Authors also discuss a number of competing protocols that have come out of various Web services standard committees, and why each one is needed. Future trends in Web services is the last topic discussed in the text with a brief talk of Web semantics.
All and all, this is a great book on Web service protocols - the topics are easy to read and follow - something that each and everyone one of us involved with Web services can use given the number of protocols and standards that are out there.
|
 Too high level ( neeumeeu )
There are several other books, that are over 2 years old that do the same job as this book. As an SOA enthusiast, you probably own or have read several of them already .. why bother with another one?
|
|
|
|
|
|
Addiction
