[prev in list] [next in list] [prev in thread] [next in thread]
List: pear-doc
Subject: [PEAR-DOC] cvs: peardoc /en/guide/migrating/channels xml.xml
From: "Brett Bieber" <saltybeagle () php ! net>
Date: 2008-02-22 18:08:49
Message-ID: cvssaltybeagle1203703729 () cvsserver
[Download RAW message or body]
saltybeagle Fri Feb 22 18:08:49 2008 UTC
Modified files:
/peardoc/en/guide/migrating/channels xml.xml
Log:
Correct the description of <rest><baseurl> elements in channel.xml -- replace \
XMLRPC with REST in a few instances to reflect the dropped XMLRPC support.
http://cvs.php.net/viewvc.cgi/peardoc/en/guide/migrating/channels/xml.xml?r1=1.2&r2=1.3&diff_format=u
Index: peardoc/en/guide/migrating/channels/xml.xml
diff -u peardoc/en/guide/migrating/channels/xml.xml:1.2 \
peardoc/en/guide/migrating/channels/xml.xml:1.3
--- peardoc/en/guide/migrating/channels/xml.xml:1.2 Sat Mar 26 06:08:04 2005
+++ peardoc/en/guide/migrating/channels/xml.xml Fri Feb 22 18:08:47 2008
@@ -1,4 +1,4 @@
-<!-- $Revision: 1.2 $ -->
+<!-- $Revision: 1.3 $ -->
<refentry id="guide.migrating.channels.xml">
<refnamediv>
<refname>channel.xml</refname>
@@ -72,8 +72,8 @@
<function version="1.0">channel.listAll</function>
</xmlrpc>
<link linkend="guide.migrating.channels.xml.protocols"><rest></link> \
<!-- no default path, all must be defined in baseurl -->
- <baseurl type="package">http://pear.example.com/rest/1.0/package</baseurl>
- <baseurl type="category">http://pear.example.com/rest/1.0/category</baseurl>
+ <baseurl type="REST1.0">http://pear.example.com/rest/</baseurl>
+ <baseurl type="REST1.1">http://pear.example.com/rest/</baseurl>
</rest>
<link linkend="guide.migrating.channels.xml.protocols"><soap</link> \
path="soapy.php"> <!-- default path is soap.php \
-->
<function version="1.0">package.listAll</function>
@@ -91,7 +91,7 @@
<function version="1.0">package.search</function>
</xmlrpc>
<rest> <!-- no default path, all must be defined in baseurl -->
- <baseurl type="package">http://foo2.example.com/rest/1.0/package</baseurl>
+ <baseurl type="REST1.0">http://foo2.example.com/rest/</baseurl>
</rest>
</mirror>
</servers>
@@ -226,9 +226,9 @@
<title><xmlrpc>, <soap>, <rest></title>
<para>
channel.xml knows about the XML-RPC, SOAP, and REST protocols for web services.
- However, the PEAR installer only supports XML-RPC currently, and may support
- REST shortly. No support for SOAP is planned for the near future. However, \
should
- it ever be implemented, channel.xml is ready.
+ However, the PEAR installer only supports REST currently, and may support
+ other methods in the future. No support for SOAP is planned for the near \
future. + However, should it ever be implemented, channel.xml is ready.
</para>
<para>
The <xmlrpc> and <soap> tags have identical formats. Both tags can \
contain @@ -244,8 +244,8 @@
The <rest> tag reflects the design concept behind REST: each resource is
defined by a base URL in tag <baseurl> that is then used by the installer
along with hyperlinks to glean the same information that XML-RPC or SOAP would
- provide. Required attribute "type" tells the installer what kind of
- information is provided by the base URL, and how to parse that information.
+ provide. Required attribute "type" tells the installer what version \
of + the PEAR installer REST interface is provided at the base URL.
</para>
<refsect3 id="guide.migrating.channels.xml.protocols.function">
<title><function></title>
--
PEAR Documentation List Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic