RESTful Web Services(英文影印版)
点击看大图基本信息
- 原书名： RESTful Web Services
- 原出版社： O'Reilly Media, Inc.
编辑推荐
“每一位Web开发者都需要阅读这本书。”
—— David Heinemeier Hansson，Rails框架创始人
“《RESTful Web Services》为构建包含Web的服务，提供了一张具有实际意义的发展路线图，而不是绕着目标兜圈子。”
—— Adam Trachtenberg，PHP作者及eBay公司Web services传道者
推荐阅读
内容简介回到顶部↑
书籍
计算机书籍
你也许曾经建立过可供他人使用的网站，但是，你能否创建可供机器使用的网站？万维网（world wide web）不仅仅只是一个巨大的分布式应用——应该把它视为一个分布式计算平台。web services、聚合（mashup）和ajax应用都以web作为平台。而今天的web services技术早已失去了web赖以成功的简洁性，它们并不像web那样工作，并且正日益丧失其原有的优势。
本书让“web”回归web services。它阐述了如何以你日常所使用的技术访问可编程的web。其关键就在于rest，它是驱动web的架构样式。本书包括以下内容：
·强调web基础技术的力量 —— http应用协议、uri命名标准与xml标记语言
·介绍面向资源的架构（roa），设计restful web services的常识规则集合
·揭示restful的设计如何比远程过程调用（rpc）更为简单、具有更多功能以及扩展性
·包含restful web services的真实案例，如amazon的简单存储服务与atom发布协议等
·探讨各种流行编程语言的web services客户端
·展示如何用三种流行框架实现restful services —— ruby on rails、restlet（基于java）和django（基于python）
·关注实际问题，诸如怎样设计和实现restful web services与客户端等
《restful web services》是对真实web services运用rest设计哲学的第一本书。它为你的成功设计树立了最佳实践典范，也为你提供了将设计转化为代码所需的技术。你不妨充分利用可编程web的力量——只要与web合作，而不是与之抵抗。本书将教会你一切。
计算机书籍
你也许曾经建立过可供他人使用的网站，但是，你能否创建可供机器使用的网站？万维网（world wide web）不仅仅只是一个巨大的分布式应用——应该把它视为一个分布式计算平台。web services、聚合（mashup）和ajax应用都以web作为平台。而今天的web services技术早已失去了web赖以成功的简洁性，它们并不像web那样工作，并且正日益丧失其原有的优势。
本书让“web”回归web services。它阐述了如何以你日常所使用的技术访问可编程的web。其关键就在于rest，它是驱动web的架构样式。本书包括以下内容：
·强调web基础技术的力量 —— http应用协议、uri命名标准与xml标记语言
·介绍面向资源的架构（roa），设计restful web services的常识规则集合
·揭示restful的设计如何比远程过程调用（rpc）更为简单、具有更多功能以及扩展性
·包含restful web services的真实案例，如amazon的简单存储服务与atom发布协议等
·探讨各种流行编程语言的web services客户端
·展示如何用三种流行框架实现restful services —— ruby on rails、restlet（基于java）和django（基于python）
·关注实际问题，诸如怎样设计和实现restful web services与客户端等
《restful web services》是对真实web services运用rest设计哲学的第一本书。它为你的成功设计树立了最佳实践典范，也为你提供了将设计转化为代码所需的技术。你不妨充分利用可编程web的力量——只要与web合作，而不是与之抵抗。本书将教会你一切。
目录回到顶部↑
foreword
preface
1. the programmable web and its inhabitants
kinds of things on the programmable web
http: documents in envelopes
method information
scoping information
the competing architectures
technologies on the programmable web
leftover terminology
2. writing web service clients
web services are web sites
del.icio.us: the sample application
making the request: http libraries
processing the response: xml parsers
json parsers: handling serialized data
clients made easy with wadl
3. what makes restful services different?
introducing the simple storage service
object-oriented design of s3
preface
1. the programmable web and its inhabitants
kinds of things on the programmable web
http: documents in envelopes
method information
scoping information
the competing architectures
technologies on the programmable web
leftover terminology
2. writing web service clients
web services are web sites
del.icio.us: the sample application
making the request: http libraries
processing the response: xml parsers
json parsers: handling serialized data
clients made easy with wadl
3. what makes restful services different?
introducing the simple storage service
object-oriented design of s3
前言回到顶部↑
We wrote this book to tell you about an amazing new technology. It’s here, it’s hot, and it promises to radically change the way we write distributed systems. We’re talking about the World Wide Web. .
Okay, it’s not a new technology. It’s not as hot as it used to be, and from a technical standpoint it’s not incredibly amazing. But everything else is true. In 10 years the Web has changed the way we live, but it’s got more change left to give. The Web is a simple, ubiquitous, yet overlooked platform for distributed programming. The goal of this book is to pull out that change and send it off into the world.
It may seem strange to claim that the Web’s potential for distributed programming has been overlooked. After all, this book competes for shelf space with any number of other books about web services. The problem is, most of today’s “web services” have nothing to do with the Web. In opposition to the Web’s simplicity, they espouse a heavyweight architecture for distributed object access, similar to COM or CORBA. Today’s “web service” architectures reinvent or ignore every feature that makes the Web successful. It doesn’t have to be that way. We know the technologies behind the Web can drive useful remote services, because those services exist and we use them every day. We know such services can scale to enormous size, because they already do. Consider the Google search engine. What is it but a remote service for querying a massive database and getting back a formatted response? We don’t normally think of web sites as “services,” because that’s programming talk and a web site’s ultimate client is a human, but services are what they are. ..
Every web application—every web site—is a service. You can harness this power for programmable applications if you work with the Web instead of against it, if you don’t bury its unique power under layers of abstraction. It’s time to put the “web” back into “web services.”
The features that make a web site easy for a web surfer to use also make a web service API easy for a programmer to use. To find the principles underlying the design of these services, we can just translate the principles for human-readable web sites into terms that make sense when the surfers are computer programs.
That’s what we do in this book. Our goal throughout is to show the power (and, where appropriate, the limitations) of the basic web technologies: the HTTP application protocol, the URI naming standard, and the XML markup language. Our topic is the set of principles underlying the Web: Representational State Transfer, or REST. For the first time, we set down best practices for “RESTful” web services. We cut through the confusion and guesswork, replacing folklore and implicit knowledge with concrete advice.
We introduce the Resource-Oriented Architecture (ROA), a commonsense set of rules for designing RESTful web services. We also show you the view from the client side: how you can write programs to consume RESTful services. Our examples include realworld RESTful services like Amazon’s Simple Storage Service (S3), the various incarnations of the Atom Publishing Protocol, and Google Maps. We also take popular services that fall short of RESTfulness, like the del.icio.us social bookmarking API, and rehabilitate them. ...
Okay, it’s not a new technology. It’s not as hot as it used to be, and from a technical standpoint it’s not incredibly amazing. But everything else is true. In 10 years the Web has changed the way we live, but it’s got more change left to give. The Web is a simple, ubiquitous, yet overlooked platform for distributed programming. The goal of this book is to pull out that change and send it off into the world.
It may seem strange to claim that the Web’s potential for distributed programming has been overlooked. After all, this book competes for shelf space with any number of other books about web services. The problem is, most of today’s “web services” have nothing to do with the Web. In opposition to the Web’s simplicity, they espouse a heavyweight architecture for distributed object access, similar to COM or CORBA. Today’s “web service” architectures reinvent or ignore every feature that makes the Web successful. It doesn’t have to be that way. We know the technologies behind the Web can drive useful remote services, because those services exist and we use them every day. We know such services can scale to enormous size, because they already do. Consider the Google search engine. What is it but a remote service for querying a massive database and getting back a formatted response? We don’t normally think of web sites as “services,” because that’s programming talk and a web site’s ultimate client is a human, but services are what they are. ..
Every web application—every web site—is a service. You can harness this power for programmable applications if you work with the Web instead of against it, if you don’t bury its unique power under layers of abstraction. It’s time to put the “web” back into “web services.”
The features that make a web site easy for a web surfer to use also make a web service API easy for a programmer to use. To find the principles underlying the design of these services, we can just translate the principles for human-readable web sites into terms that make sense when the surfers are computer programs.
That’s what we do in this book. Our goal throughout is to show the power (and, where appropriate, the limitations) of the basic web technologies: the HTTP application protocol, the URI naming standard, and the XML markup language. Our topic is the set of principles underlying the Web: Representational State Transfer, or REST. For the first time, we set down best practices for “RESTful” web services. We cut through the confusion and guesswork, replacing folklore and implicit knowledge with concrete advice.
We introduce the Resource-Oriented Architecture (ROA), a commonsense set of rules for designing RESTful web services. We also show you the view from the client side: how you can write programs to consume RESTful services. Our examples include realworld RESTful services like Amazon’s Simple Storage Service (S3), the various incarnations of the Atom Publishing Protocol, and Google Maps. We also take popular services that fall short of RESTfulness, like the del.icio.us social bookmarking API, and rehabilitate them. ...
加载中...
