Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Client and Server port

 
Qusay Jaafar
Ranch Hand
Posts: 127
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If an administrator able to change the server port for some reason,
then clients need to know about this change.
(I don't think this will be programmetically. what I mean
here is this administrator need to tell all his clients by
phone or whatever). At that time clients will change their port too.
Shall I implement this senario or leave it for its default port.
Which is easier of course...
Any idea...
 
Andrew Monkhouse
author and jackaroo
Marshal Commander
Pie
Posts: 12014
220
C++ Firefox Browser IntelliJ IDE Java Mac Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Qusay
From memory Mark just used the standard port, and didn't allow it to be changed. And he got good marks for his submission.
However in a real environment I would insist on one or more of the following:
  • allowing the port number to be changed
  • allowing our application to register with an external rmi registry
  • allowing other applications to register with our registry


  • I had all three capabilities in my application (actually I only described what needed to be done to security to allow the third, but I tested it and it did work).
    It is a question on whether you follow the concept of "simplest thing that will allow you to pass" or whether you follow the "make the system as user friendly as possible". Or a compromise between the two.
    Whatever you do: Document it!
    Regards, Andrew
     
    • Post Reply
    • Bookmark Topic Watch Topic
    • New Topic