URLyBird 1.2.2 modes

[Bj�rn Tikkanen]

My assignment says "The mode flag must be either "server", indicating the server program must run, "alone", indicating standalone mode, or left out entirely, in which case the network client and gui must run."

I interpret this as
server - start RMI server
alone - start Client GUI in local mode
left out - start RMI server and Client GUI in network mode

Or, should you in alone mode be able to say if to connect to RMI server or local file?

[Gabriel Vargas]

Hi Bj�rn

I interpret this as
server - start RMI server
alone - start Client GUI in local mode
left out - start RMI server and Client GUI in network mode

Mmmm, i have a different interpretation (i take my interpretation of Andrew's book ):

server - start RMI server (asking for datafile path, and port number)
letf out - Start network client (asking for ip server and port number)
alone - start server in local mode (asking for datafile path) and later client in local mode (no RMI)

Look this forum, it brings you more ideas about parameters:

https://coderanch.com/t/188274/java-developer-SCJD/certification/suncertify-properties

I hope it helps you.

[Bj�rn Tikkanen]

Originally posted by Juan Gabriel Vargas Bola�os:


server - start RMI server (asking for datafile path, and port number)
letf out - Start network client (asking for ip server and port number)
alone - start server in local mode (asking for datafile path) and later client in local mode (no RMI)

Look this forum, it brings you more ideas about parameters:

Ok, I think this is what I meant as well with one exception. For the alone part, is there really a server started in this mode? Sure, there should be a screen for settings input (database location) but is there a must for a "server" to be started? If the definition of server is the database part I can agree, but otherwise I think I'm off track here.

[Gabriel Vargas]

I mean if your server is designed to be executed standalone or remote you can initialize that with different parameters for each mode bu with the same basic functionality (decouple functionality from communication). Then if your mode is alone initialize client standalone.

[Beny Na]

"alone - start server in local mode (asking for datafile path) and later client in local mode (no RMI)"
-------------------------
what does it mean, i don't think we have to start the server for alone mode
that statement above confuse me, i don't see it on my assignment specs, maybe mine is different with yours

Thank you

[Mark Smyth]

Originally posted by Beny Na:
"alone - start server in local mode (asking for datafile path) and later client in local mode (no RMI)"
-------------------------
what does it mean, i don't think we have to start the server for alone mode
that statement above confuse me, i don't see it on my assignment specs, maybe mine is different with yours

Thank you

Alone: Gui part + DB access part;
Server: Remote Server part + DB access part;
None: Gui part;

Exactly where your server part ends and the data access part begins heavily depends on your implementation.

[Bj�rn Tikkanen]

Originally posted by Mark Smyth:


Alone: Gui part + DB access part;
Server: Remote Server part + DB access part;
None: Gui part;

Exactly where your server part ends and the data access part begins heavily depends on your implementation.

Hi Mark

This is also what I have implemented after a few test with different versions. I got it quite wrong in the beginning, but to be able to start both GUI and RMI Server part independent and on differnt machines this aproach make sense.

Thank you all for all input!