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.
What I must write in choces.txt about Network Connection Protocol?
I have considered possible variants of realisation: RMI or Sockets with Serialized Objects. I am familiar with both approaches.
I have chosen RMI.
In the choces.txt I have described why I have chosen RMI and what lacks at it is. At me it has turned out only 10 lines. It seems to me what is it very little (Data Access Design occupies 115 lines).
What I still can write there?
I mentioned 8 advantages and 3 disadvantages about the networking protocol I used (RMI). This took approximately 40 lines. Furthermore I have +- 100 lines to describe the consequences on my project (with regard to client identification, because the interface I had to implement didn't have a lockCookie).
Check the SCJD Forum FAQ and also read Chapter 5 of the Monkhouse book.
Joined: May 20, 2010
Roel De Nijs wrote:
Furthermore I have +- 100 lines to describe the consequences on my project (with regard to client identification, because the interface I had to implement didn't have a lockCookie).
As far as I understand, not all have a cookie. But in my case, the locking mechanism is contained in SunInterface and there is no difference which approach to use.