choces.txt / Network Connection Protocol

Hi all,

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?

Hi David,

David Kachen wrote:What I still can write there?

Advantages and disadvantages of each.

How your choice achieve the main design goals of your assignment:
Ease of use and extending your code, junior programmer maintaining your code learning curve, etc.

How do you solve identifying a client for logical record locking in each approach.

HTH,

Carlos.

David Kachen wrote: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).

Hi Carlos,

Carlos Morillo wrote:
How do you solve identifying a client for logical record locking in each approach.

I do not understand what you mean.

In my implementation, the record lock/unlock will be the same for all approaches. All logic is implemented in data access class (Data), which does not depend on network transport.

Check the SCJD Forum FAQ and also read Chapter 5 of the Monkhouse book.

Hi Roel,

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.

David Kachen wrote:As far as I understand, not all have a cookie.

Indeed, have a look here.

Ooh - is there a 'minimum size' on choices.txt that I'm unaware of? I just have like 2 sentences describing what I did (implement both RMI and sockets), and why I chose what I did (RMI).

My whole 'choices.txt' file is like 4 pages, printed. Do you think that perhaps that area of my submission is underpowered?

No, not a minimum size. Here you can find someone with an ultra limited choices.txt (I had 36 KB), no idea how many pages that is.

My choices.txt is 35K and userguide.txt is 10K.

No, not a minimum size. Here you can find someone with an ultra limited choices.txt (I had 36 KB), no idea how many pages that is.

Roel are you making fun of me

Hey Peter, did you pass? And how big did your choices.txt end up being?

Mine's very concise as well. I didn't describe the system design in it, I just made entries when I ran into difficult design or implementation choices.

Hi Cindy.

No I havent submited yet... still working on it. My choices will probably be aprox like everybody elses in the end.

BR
/Peter

Hi all,

I have used Roel council about "Network choices". And now my choces.txt has increased for 100 lines. It wasn't easy.

Thanks Roel.