Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

NX: I am stupid enuff to understand the instruction

 
Arun Kumar
Ranch Hand
Posts: 67
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This is the block of instruction given for the contractor project under non-networked mode.
Non-Networked Mode
-------------------
The program must be able to work in a non-networked mode. In this mode, the database and GUI must run in the same VM and must perform no networking, must not use loopback networking, and must not involve the serialization of any objects when communicating between the GUI and database elements.
The operating mode is selected using the single command line argument that is permitted. Architecturally, this mode must use the database and GUI from the networked form, but must not use the network server code at all.
</end>
I understand the first paragraph perfectly. (Cannot use the ip of the remote machine as 127.0.0.1 and there by loop back to your own machine using RMI/Socket).
But in the second paragraph, "Architecturally, this mode must use the database and GUI from the networked form" confuses me. So the database must be in a different machine, but cannot use networking? How is that possible.
Or in the non-networked mode, both GUI and the database should run off the same machine?
 
Andrew Monkhouse
author and jackaroo
Marshal Commander
Pie
Posts: 11854
185
C++ Firefox Browser IntelliJ IDE Java Mac Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Ken,
Architecturally, this mode must use the database and GUI from the networked form, but must not use the network server code at all.

My reading is that they are telling you that you must only have one GUI and one database. You cannot have a "networked GUI application" and a separate "non networked GUI application". Likewise you cannot have a "networked database" and a "non networked database".
Perhaps another way of looking at it is to think of modules: You will have one module for the GUI, one module for the datbase, and one replacable module for either network access or local access.
Does this make sense of it?
Regards, Andrew
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic