Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Is it okay to admit that I don't know RMI?

 
Ranch Hand
Posts: 124
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi ranchers,

I am at the stage of writing my choices.txt contents. I am currently stuck at whether I should give "I don't know RMI" as a justification to the choice of implementing my program's network connection. Should I admit it or don't state it and just come up with some other reasons?

Regards
Clivant
 
Ranch Hand
Posts: 64
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Clivant,

Why admit you don't know it? Instead of saying you don't know RMI say you prefer sockets over RMI because you have more experience with sockets and they are better suited to your application because ...

No need to lie but no need to point out your flaws either.

Steven
 
Ranch Hand
Posts: 1033
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by Clivant Yeo:
Hi ranchers,

I am at the stage of writing my choices.txt contents. I am currently stuck at whether I should give "I don't know RMI" as a justification to the choice of implementing my program's network connection. Should I admit it or don't state it and just come up with some other reasons?

Regards
Clivant



You should learn RMI and try it, its much easier than sockets. That said, I'm using sockets because I get control of the network connections and threading. I'm implementing a rich client and don't want to set up a single connection that ties up a port for the entire time the client is up, nor do I want to make a seperate connection for each database command. I want to use one connection for every business command such as find-all or book. Sockets give me the control over this. I can guarantee that the sequence {lock, read, update, unlock} all takes place using the same server thread. This is not possible with RMI.

If your project uses locking cookies and you don't plan to handle orphaned locks and lost connections this doesn't matter. But it is a big advantage of sockets.

If you have chosen to go the thin client route, you should definitely use RMI as it will result in much simpler code.
 
To do a great right, do a little wrong - shakepeare. twisted little ad:
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
    Bookmark Topic Watch Topic
  • New Topic