Referee 1 **************************************************************** This a nicely written paper with a clear problem definition and a proposed solution. However, the following issues need to be addressed to make the paper more strong: The motivation for not having the remote interfaces (or proxies) on client's machine are not very convincing. It would have been better if a comparative study was made between the author's approach and other alternatives, such as dynamic invocation (e.g., allowed by CORBA). Various issues such as space, consistency, and performance need to be looked into for such a comparison. The idea of using wrapper is not really new, although, it has been used in different ways than what the paper is proposing. An interesting issue to look into would be the amount of effort needed to create these wrappers for more complex problems than the ones described in the paper. Finally, more details are needed (e.g., performance comparison between the standalone and the distributed case) that can validate the claims the authors are making in the conclusion. Referee 2 **************************************************************** E: Referee Comments (For Author and Editor) I am not sure that the problem posed (i.e. instantiating a remote object and using it in remote or local calls) is a major problem in O-O distributed systems (based on RMI, CORBA or JINI), except where access to the server source code is not available or is in a non-Java language. In RMI, object serialisation allows objects to be passed from client to server and vica versa and in CORBA, object references are available through the Naming Service (also the CORBA 3 Objects-by-value facility will help here). Normally, you would want servers to be instantiated independently of clients, although there are occassions where a client invoked server is very useful. Some of the same functionality presented could also probably be obtained on the client side using the new Java Proxy generator class. However, the techniques presented here are interesting and useful and could simplify the design of some distributed systems. They could also be particularly useful in the design of wrappers for remote non-Java objects. F: Presentation Changes I copied the source code listings and compiled them, but some editing (e.g. of capital P's in Public) is required. It would be useful if the complete code were made available generally (you need authorized login to access it). Referee 3 **************************************************************** Referee 4 **************************************************************** Referee 5 ****************************************************************