This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I have read my topic discussing usage of RMI. Actaully, is there's anyone using socket instead? Why RMI is so popularly be used? In my design, running of ther server side only need to use command-line instruction. Is any GUI required for the server side?
Originally posted by James Lee: I have read my topic discussing usage of RMI. Actaully, is there's anyone using socket instead? Why RMI is so popularly be used?
Very few opt for sockets. My assessment at the time was that, if you would choose to use sockets, you would find yourself essentially doing all the things that RMI does for you. And a good programmer is a lazy programmer
In my design, running of ther server side only need to use command-line instruction. Is any GUI required for the server side?
You don't need a server-side GUI. In fact I think it's a positively bad idea -- in the real world, server applications often run on Unix servers that do not necessarily have a graphical (X11) display. In fact I personally have had lots of of grief with a (non-Java) server application that insisted on having an X11 server to talk to. For some reason a dummy X11 server would not build on the machine, so we used an X11 terminal. Whenever anyone switched it off, deliberately or by bumping into it, the whole back-end would go down with it. The whole miserable episode was concluded only when we shoved a graphics card in the server. Grrrrr. But that is entirely by the by Peter's tip for the day is: if your server does not absolutely need a GUI, make sure that it supports GUI-less operation. - Peter