[prev in list] [next in list] [prev in thread] [next in thread]
List: webservices-general
Subject: Re: [VOTE] XML-RPC 3.1
From: Anil Saldhana <anilsaldhana () yahoo ! com>
Date: 2007-08-09 14:37:14
Message-ID: 659074.57487.qm () web52111 ! mail ! re2 ! yahoo ! com
[Download RAW message or body]
+1 from me, Jochen. :)
Ruchith Fernando <ruchith.fernando@gmail.com> wrote: +1 from me!
Thanks,
Ruchith
On 8/8/07, Jochen Wiedmann wrote:
>
> [Resending this to general@ again, because we need so far we've
> only got two votes from PMC member. Seems, the best argument
> for me to be on the PMC is to save me from yet another reminder,
> because my vote counts ...]
>
>
> Hi,
>
> after one year since the release of XML-RPC 3.0, I'd like to call for
> the next release, to be called XML-RPC 3.1, based on revision 561948.
>
> The list of changes since 3.0 is, IMO, impressive, and shows that 3.1
> will be highly recommendable over 3.1.
>
> A current snapshot has been deployed to the Maven 2 repository. See
>
>
> http://people.apache.org/repo/m2-snapshot-repository/org/apache/xmlrpc/xmlrpc-server/
>
> The proposed site and the proposed distribution is available at
>
> http://people.apache.org/~jochen/xml-rpc
>
>
> Jochen
>
> [ ] +1
> [ ] =0
> [ ] -1
>
>
>
>
>
> - Added support for void methods, if extensions are turned on.
> - Added PropertyHandlerMapping.load(ClassLoader, Map). (Perry Nguyen)
> - The authentication handler, type converter and requestprocessor
> factories are now configurable as properties of the XmlRpcServlet.
> (Jimisola Laursen)
> - Atomic properties of XmlRpcServer are now configurable as init
> parameters in the XmlRpcServlet.
> - Reworked the WebServer/ThreadPool framework in order to ensure a
> clean shutdown.
> - Introduced the method
> AbstractReflectiveHandlerMapping.isHandlerMethod().
> This should allow users to prevent remote invocation of certain
> methods, for example initialization stuff.
> - The ClientFactory is now able to use a custom name for the remote
> handler. So far, it was always using the interface name.
> (Eugene Prokopiev)
> - It is now possible to have other objects than strings as
> map keys.
> - Made extending the XmlRpcCommonsTransportFactory easier.
> (Steffen Pingel)
> - Added support for redirects. (Andrew Norman)
> - An invalid dateTime value is now causing a more informative
> error message.
> - Address matching in the Webserver wasn't actually working,
> because casting of integers to bytes was implemented wrong.
> (Gamaliel Amaudruz)
> - Make the HttpClient creation in XmlRpcCommonsTransport and the
> URLConnection creation in XmlRpcSunHttpTransport protected.
> This is required for cookie support.
> - The WebServer was producing invalid error responses, if
> contentLengthOptional was set.
> - If the server was throwing an XmlRpcException, then the fault code
> and fault string weren't given to the client.
> (Juha Syrjala)
> - The WebServer replies with an HTTP error 401 now, if the
> client uses chunked encoding.
> - The properties "Extension-Name", "Specification-Vendor",
> "Specification-Version", "Specification-Title",
> "Implementation-Vendor-Id", "Implementation-Vendor" and
> "Implementation-Version" are now present in the MANIFEST files.
> - An NPE was thrown, if the clients request didn't contain a "params"
> element.
> - The method TimingOutCallback.waitForResponse is now checking, whether
> a response has already arrived before waiting. (Jonathan Oexner)
> - Fixed a serious performance problem, if the XML parser was sending
> large content in small pieces. This could happen, for example, if
> the content contained a large number of character entities.
> - The configuration of the reply timeout in the commons transport was
> wrong. (Juho Yli-Krekola)
> - The DateParser is now treating an empty string as null. (Carsten
> Wolters)
> - The XmlRpcRequestParser and XmlRpcResponseParser didn't reset
> their internal state within startDocument(). Consequently, they
> haven't been reusable. (Keith McNeill)
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
> For additional commands, e-mail: general-help@ws.apache.org
>
>
--
www.ruchith.org
www.wso2.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
For additional commands, e-mail: general-help@ws.apache.org
---------------------------------
Boardwalk for $500? In 2007? Ha!
Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games.
[Attachment #3 (text/html)]
+1 from me, Jochen. :)<br><br><b><i>Ruchith Fernando \
<ruchith.fernando@gmail.com></i></b> wrote:<blockquote class="replbq" \
style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: \
5px;"> +1 from me!<br><br>Thanks,<br>Ruchith<br><br>On 8/8/07, Jochen Wiedmann \
<jochen.wiedmann@softwareag.com> wrote:<br>><br>> [Resending this to general@ \
again, because we need so far we've<br>> only got two votes from PMC member. \
Seems, the best argument<br>> for me to be on the PMC is to save me from yet \
another reminder,<br>> because my vote counts ...]<br>><br>><br>> \
Hi,<br>><br>> after one year since the release of XML-RPC 3.0, I'd like to call \
for<br>> the next release, to be called XML-RPC 3.1, based on revision \
561948.<br>><br>> The list of changes since 3.0 is, IMO, impressive, and shows \
that 3.1<br>> will be highly recommendable over 3.1.<br>><br>> A current \
snapshot has been deployed to the Maven 2 repository. See<br>><br>><br>> \
http://people.apache.org/repo/m2-snapshot-repository/org/apache/xmlrpc/xmlrpc-server/<br>><br>> \
The proposed site and the proposed distribution is available at<br>><br>> \
http://people.apache.org/~jochen/xml-rpc<br>><br>><br>> \
Jochen<br>><br>> [ ] +1<br>> [ ] =0<br>> [ ] \
-1<br>><br>><br>><br>><br>><br>> - Added support for void methods, \
if extensions are turned on.<br>> - Added PropertyHandlerMapping.load(ClassLoader, \
Map). (Perry Nguyen)<br>> - The authentication handler, type converter and \
requestprocessor<br>> factories are now configurable as properties of the \
XmlRpcServlet.<br>> (Jimisola Laursen)<br>> - Atomic properties of \
XmlRpcServer are now configurable as init<br>> parameters in the \
XmlRpcServlet.<br>> - Reworked the WebServer/ThreadPool framework in order to \
ensure a<br>> clean shutdown.<br>> - Introduced the method<br>> \
AbstractReflectiveHandlerMapping.isHandlerMethod().<br>> This should allow \
users to prevent remote invocation of certain<br>> methods, for example \
initialization stuff.<br>> - The ClientFactory is now able to use a custom name \
for the remote<br>> handler. So far, it was always using the interface \
name.<br>> (Eugene Prokopiev)<br>> - It is now possible to have other \
objects than strings as<br>> map keys.<br>> - Made extending the \
XmlRpcCommonsTransportFactory easier.<br>> (Steffen Pingel)<br>> - Added \
support for redirects. (Andrew Norman)<br>> - An invalid dateTime value is now \
causing a more informative<br>> error message.<br>> - Address matching in \
the Webserver wasn't actually working,<br>> because casting of integers to \
bytes was implemented wrong.<br>> (Gamaliel Amaudruz)<br>> - Make the \
HttpClient creation in XmlRpcCommonsTransport and the<br>> URLConnection \
creation in XmlRpcSunHttpTransport protected.<br>> This is required for cookie \
support.<br>> - The WebServer was producing invalid error responses, if<br>> \
contentLengthOptional was set.<br>> - If the server was throwing an \
XmlRpcException, then the fault code<br>> and fault string weren't given to the \
client.<br>> (Juha Syrjala)<br>> - The WebServer replies with an HTTP error \
401 now, if the<br>> client uses chunked encoding.<br>> - The properties \
"Extension-Name", "Specification-Vendor",<br>> "Specification-Version", \
"Specification-Title",<br>> "Implementation-Vendor-Id", "Implementation-Vendor" \
and<br>> "Implementation-Version" are now present in the MANIFEST \
files.<br>> - An NPE was thrown, if the clients request didn't contain a \
"params"<br>> element.<br>> - The method TimingOutCallback.waitForResponse \
is now checking, whether<br>> a response has already arrived before waiting. \
(Jonathan Oexner)<br>>
- Fixed a serious performance problem, if the XML parser was sending<br>> \
large content in small pieces. This could happen, for example, if<br>> the \
content contained a large number of character entities.<br>> - The configuration \
of the reply timeout in the commons transport was<br>> wrong. (Juho \
Yli-Krekola)<br>> - The DateParser is now treating an empty string as null. \
(Carsten<br>> Wolters)<br>> - The XmlRpcRequestParser and \
XmlRpcResponseParser didn't reset<br>> their internal state within \
startDocument(). Consequently, they<br>> haven't been reusable. (Keith \
McNeill)<br>><br>><br>><br>><br>><br>> \
---------------------------------------------------------------------<br>> To \
unsubscribe, e-mail: general-unsubscribe@ws.apache.org<br>> For additional \
commands, e-mail: general-help@ws.apache.org<br>><br>><br><br><br>-- \
<br>www.ruchith.org<br>www.wso2.org<br><br>---------------------------------------------------------------------<br>To \
unsubscribe, e-mail: general-unsubscribe@ws.apache.org<br>For additional commands, \
e-mail: general-help@ws.apache.org<br><br></jochen.wiedmann@softwareag.com></blockquote><br><p> 
<hr size=1>Boardwalk for $500? In 2007? Ha! <br><a \
href="http://us.rd.yahoo.com/evt=48223/*http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow">Play \
Monopoly Here and Now</a> (it's updated for today's economy) at Yahoo! Games.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic