[ http://issues.apache.org/jira/browse/XMLRPC-46?page=all ]
Jochen Wiedmann closed XMLRPC-46:
---------------------------------
Resolution: Fixed
Assign To: (was: rpc-dev mailing list)
See http://people.apache.org/~jochen/xmlrpc/site/
> Use List interface instead of Vector
> ------------------------------------
>
> Key: XMLRPC-46
> URL: http://issues.apache.org/jira/browse/XMLRPC-46
> Project: XML-RPC
> Type: Bug
> Components: Source
> Versions: 1.1
> Environment: Operating System: All
> Platform: All
> Reporter: Andriy Rozeluk
>
> When declaring methods to be executed via XML-RPC, it would be beneficial to
> remove the tight coupling on the Vector class and instead use List.
> That way, it would be possible for the classes (client, server and XML-RPC
> itself) to choose the appropriate implementation for their specific needs, but
> should not impact the code much.
> For instance, while building a list of parameters (which normally would be
> sent
> as a Vector parameter into the method), I can think of several instances where
> it would be more efficient on the client to use LinkedList (or ArrayList)
> instead, in order to manipulate the list. However, on the server side the
> method
> could just check for List, and XML-RPC would be free to create it as a Vector
> as
> it does now.
> Same thing on the server side when building a List which will be returned back
> to the client when the method returns.
> Unfortunately at this point XML-RPC will not call a method that uses List in
> the
> parameter list, and will not accept a return value of type List.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
