DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22180>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22180 Use List interface instead of Vector Summary: Use List interface instead of Vector Product: XML-RPC Version: 1.1 Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Source AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] 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.
