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.
Originally posted by Dannie Kjeldgaard: I decided to try implementing my solution with RMI, which I have never tried to use before. it seems very simple to implement, which will not be a problem. My question is more general:
Do you usually implement the ServicesImpl class as a singleton, or is it more common to allow more of those?
Best regards Dannie
Can I take it that your ServicesImpl class is the network database server? In general I would say that unless you are absolutely certain that there can only ever be one instance of a class then it is best not to implement the singleton pattern. Instead if you bind only one such object to the rmi registry instead there will be only one instance of the ServicesImpl for remote clients to access anyway.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com