1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
|
<?xml version="1.0" encoding="UTF-8"?>
<!-- Reviewed: no -->
<sect1 id="zend.rest.introduction">
<title>Introduction</title>
<para>
REST Web Services use service-specific <acronym>XML</acronym> formats. These ad-hoc
standards mean that the manner for accessing a REST web service is
different for each service. REST web services typically use <acronym>URL</acronym>
parameters (<constant>GET</constant> data) or path information for requesting data and POST
data for sending data.
</para>
<para>
Zend Framework provides both Client and Server capabilities, which,
when used together allow for a much more "local" interface experience
via virtual object property access. The Server component features
automatic exposition of functions and classes using a meaningful and
simple <acronym>XML</acronym> format. When accessing these services using the Client, it is
possible to easily retrieve the return data from the remote call. Should
you wish to use the client with a non-Zend_Rest_Server based service, it
will still provide easier data access.
</para>
<para>
In addition to <classname>Zend_Rest_Server</classname> and
<classname>Zend_Rest_Client</classname> components, <link
linkend="zend.controller.router.routes.rest"><classname>Zend_Rest_Route</classname> and
<classname>Zend_Rest_Controller</classname></link> classes are provided to aid routing
REST requests to controllers.
</para>
</sect1>
<!--
vim:se ts=4 sw=4 et:
-->
|
