🗊Презентация Restful services. Part 1. Rest pattern. Example

Категория: Устройства и комплектующие
Нажмите для полного просмотра!
Restful services. Part 1. Rest pattern. Example, слайд №1Restful services. Part 1. Rest pattern. Example, слайд №2Restful services. Part 1. Rest pattern. Example, слайд №3Restful services. Part 1. Rest pattern. Example, слайд №4Restful services. Part 1. Rest pattern. Example, слайд №5Restful services. Part 1. Rest pattern. Example, слайд №6Restful services. Part 1. Rest pattern. Example, слайд №7Restful services. Part 1. Rest pattern. Example, слайд №8Restful services. Part 1. Rest pattern. Example, слайд №9Restful services. Part 1. Rest pattern. Example, слайд №10Restful services. Part 1. Rest pattern. Example, слайд №11Restful services. Part 1. Rest pattern. Example, слайд №12Restful services. Part 1. Rest pattern. Example, слайд №13Restful services. Part 1. Rest pattern. Example, слайд №14Restful services. Part 1. Rest pattern. Example, слайд №15Restful services. Part 1. Rest pattern. Example, слайд №16Restful services. Part 1. Rest pattern. Example, слайд №17Restful services. Part 1. Rest pattern. Example, слайд №18Restful services. Part 1. Rest pattern. Example, слайд №19
Скачать
Вы можете ознакомиться и скачать презентацию на тему Restful services. Part 1. Rest pattern. Example. Доклад-сообщение содержит 19 слайдов. Презентации для любого класса можно скачать бесплатно. Если материал и наш сайт презентаций Mypresentation Вам понравились – поделитесь им с друзьями с помощью социальных кнопок и добавьте в закладки в своем браузере.

Слайды и текст этой презентации

Слайд 1


Restful services. Part 1. Rest pattern. Example
Описание слайда:
Restful services. Part 1. Rest pattern. Example

Слайд 2


What is REST? Representational State Transfer between Resource REST is a design pattern. It is a certain approach to creating Web Services. HTTP is the main and the best example of a REST style implementation
Описание слайда:
What is REST? Representational State Transfer between Resource REST is a design pattern. It is a certain approach to creating Web Services. HTTP is the main and the best example of a REST style implementation

Слайд 3


Example: Airline Reservation Service Suppose that an airline wants to create a telephone reservation system for customers to call in and make flight reservations. The airline wants to ensure that its premier members get immediate service, its frequent flyer members get expedited service and all others get regular service. There are two main approaches to implementing the reservation service...
Описание слайда:
Example: Airline Reservation Service Suppose that an airline wants to create a telephone reservation system for customers to call in and make flight reservations. The airline wants to ensure that its premier members get immediate service, its frequent flyer members get expedited service and all others get regular service. There are two main approaches to implementing the reservation service...

Слайд 4


Approach 1 "Press 1 for Premier, Press 2 for…" The airline provides a single telephone number. Upon entry into the system a customer encounters an automated message, "Press 1 if you are a premier member, press 2 if you are a frequent flyer, press 3 for all others."
Описание слайда:
Approach 1 "Press 1 for Premier, Press 2 for…" The airline provides a single telephone number. Upon entry into the system a customer encounters an automated message, "Press 1 if you are a premier member, press 2 if you are a frequent flyer, press 3 for all others."

Слайд 5


Approach 2 Telephone Numbers are Cheap! Use Them! The airline provides several telephone numbers - one number for premier members, a different number for frequent flyers, and still another for regular customers.
Описание слайда:
Approach 2 Telephone Numbers are Cheap! Use Them! The airline provides several telephone numbers - one number for premier members, a different number for frequent flyers, and still another for regular customers.

Слайд 6


Discussion In Approach 1 the answering machine introduces an extra delay, which is particularly annoying to premier members. (Doesn't everyone hate those answering systems) With Approach 2 there is no intermediate step. Premier members get instant pickup from a customer service representative. Others may have to wait for an operator.
Описание слайда:
Discussion In Approach 1 the answering machine introduces an extra delay, which is particularly annoying to premier members. (Doesn't everyone hate those answering systems) With Approach 2 there is no intermediate step. Premier members get instant pickup from a customer service representative. Others may have to wait for an operator.

Слайд 7


Web-Based Reservation Service Suppose now the airline wants to provide a Web reservation service for customers to make flight reservations through the Web. Just as with the telephone service, the airline wants to ensure that its premier members get immediate service, its frequent flyer members get expedited service, all others get regular service. There are two main approaches to implementing the Web reservation service. The approaches are analogous to the telephone service...
Описание слайда:
Web-Based Reservation Service Suppose now the airline wants to provide a Web reservation service for customers to make flight reservations through the Web. Just as with the telephone service, the airline wants to ensure that its premier members get immediate service, its frequent flyer members get expedited service, all others get regular service. There are two main approaches to implementing the Web reservation service. The approaches are analogous to the telephone service...

Слайд 8


Approach 1 One-Stop Shopping The airline provides a single URL. The Web service is responsible for examining incoming client requests to determine their priority and process them accordingly.
Описание слайда:
Approach 1 One-Stop Shopping The airline provides a single URL. The Web service is responsible for examining incoming client requests to determine their priority and process them accordingly.

Слайд 9


Approach 1 Disadvantages There is currently no industry accepted practice (rules) for expressing priorities, so rules would need to be made. The clients must learn the rule, and the Web service application must be written to understand the rule. This approach is based upon the incorrect assumption that a URL is "expensive" and that their use must be rationed. The Web service is a central point of failure. It is a bottleneck. Load balancing is a challenge. It violates Tim Berners-Lee Web Design, Axiom 0 (see next slide).
Описание слайда:
Approach 1 Disadvantages There is currently no industry accepted practice (rules) for expressing priorities, so rules would need to be made. The clients must learn the rule, and the Web service application must be written to understand the rule. This approach is based upon the incorrect assumption that a URL is "expensive" and that their use must be rationed. The Web service is a central point of failure. It is a bottleneck. Load balancing is a challenge. It violates Tim Berners-Lee Web Design, Axiom 0 (see next slide).

Слайд 10


Web Design, Axiom 0 (Tim Berners-Lee, director of W3C) Axiom 0: all resources on the Web must be uniquely identified with a URI.
Описание слайда:
Web Design, Axiom 0 (Tim Berners-Lee, director of W3C) Axiom 0: all resources on the Web must be uniquely identified with a URI.

Слайд 11


Approach 2: URLs are Cheap! Use Them! The airline provides several URLs - one URL for premier members, a different URL for frequent flyers, and still another for regular customers.
Описание слайда:
Approach 2: URLs are Cheap! Use Them! The airline provides several URLs - one URL for premier members, a different URL for frequent flyers, and still another for regular customers.

Слайд 12


Approach 2 Advantages The different URLs are discoverable by search engines and UDDI registries. It's easy to understand what each service does simply by examining the URL, i.e., it exploits the Principle of Least Surprise. There is no need to introduce rules. Priorities are elevated to the level of a URL. "What you see is what you get." It's easy to implement high priority - simply assign a fast machine at the premier member URL. There is no bottleneck. There is no central point of failure. Consistent with Axiom 0.
Описание слайда:
Approach 2 Advantages The different URLs are discoverable by search engines and UDDI registries. It's easy to understand what each service does simply by examining the URL, i.e., it exploits the Principle of Least Surprise. There is no need to introduce rules. Priorities are elevated to the level of a URL. "What you see is what you get." It's easy to implement high priority - simply assign a fast machine at the premier member URL. There is no bottleneck. There is no central point of failure. Consistent with Axiom 0.

Слайд 13


Recap We have looked at a reservation service. We have seen a telephone-based version and a Web-based version of the reservation service. With each version we have seen two main approaches to implementing the service. Which approach is the REST design pattern and which isn't? See the following slides.
Описание слайда:
Recap We have looked at a reservation service. We have seen a telephone-based version and a Web-based version of the reservation service. With each version we have seen two main approaches to implementing the service. Which approach is the REST design pattern and which isn't? See the following slides.

Слайд 14


This Ain't the REST Design Pattern
Описание слайда:
This Ain't the REST Design Pattern

Слайд 15


This is the REST Design Pattern
Описание слайда:
This is the REST Design Pattern

Слайд 16


This ain't the REST Design Pattern
Описание слайда:
This ain't the REST Design Pattern

Слайд 17


This is the REST Design Pattern
Описание слайда:
This is the REST Design Pattern

Слайд 18


Two Fundamental Aspects of the REST Design Pattern Resources Every distinguishable entity is a resource. A resource may be a Web site, an HTML page, an XML document, a Web service, a physical device, etc. URLs Identify Resources Every resource is uniquely identified by a URL. This is Tim Berners-Lee Web Design, Axiom 0.
Описание слайда:
Two Fundamental Aspects of the REST Design Pattern Resources Every distinguishable entity is a resource. A resource may be a Web site, an HTML page, an XML document, a Web service, a physical device, etc. URLs Identify Resources Every resource is uniquely identified by a URL. This is Tim Berners-Lee Web Design, Axiom 0.

Слайд 19


The Three Fundamental Aspects of the REST Design Pattern
Описание слайда:
The Three Fundamental Aspects of the REST Design Pattern

Скачать

Похожие презентации
Mypresentation.ru
Загрузить презентацию