> Better yet: let's move all the message names to static final Strings
> somewhere, so that we gain a small point in performance and a huge one
> in cleanliness. How about it?
logically, these constants should be stored in the specific class (to gain
modularity), e.g:
package org.apache.xindice.server.rpc.message;
public class DeleteDocument {
public static final String methodname =
"org.apache.xindice.server.rpc.message.DeleteDocument";
}
What bothers me a little is that in a class placed in the client package, you
will have to import org.apache.xindice.SERVER.rpc.* classes. Should a client
_import_ server classes, that's my question? I don't particularly like this
idea, but it's maybe me.
That's the reason why I thought of moving the server.rpc classes into
client.xmlrpc. And since I don't have many classes left in the server
package, I thought of removing the server package and define the "accessor"
(name to be changed) hierarchy.
-Vladimir
=====
Vladimir R. Bossicard
Apache Xindice - http://xml.apache.org/xindice
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
