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.
Hi All, I want to look at the assignment from RMI and serialization point of view. The Advanced Features of Java book from Sun says stg. like "Dont use RMI unless you see a significent benefit". So, the main adv. of RMI is clear that [BOLD]one doesn't need to encode/decode the request/response[/BOLD]; and the main disadvantage is [BOLD]being inefficient for transferring large amounts of data.[/BOLD]. I would like to hear about your insights about these two alternatives. Cheers, Ulvi
Hi Ulvi Don't forget that RMI also hides the detail of networking from you. Because it appears that you are just calling a normal method on a normal class, it can be easier for that junior programmer to understand. Using sockets will generally use fewer resources all round, not just bandwidth and numbers of messages sent, but also fewer processes on the server, and fewer maintenance threads running. The disadvantages for RMI are not a big concern in this case - we are only shipping very small messages around, and we are not expecting to have thousands of users. Have I totally failed to give you a clear idea of which one to use? Good Regards, Andrew