Client application should attempt to automatically make a connection to the server on startup.
Be aware that each vhost should run it's own server application instance, and each vhost should claim a port number. This means the server connection details should be configurable for the client. Whether this is done in code, or read from a configuration file doesn't matter.
For instance, if you wanted to connect to your local server instance if you are testing server code changes, you would connect to the subdomain and portname you claim.
nick.elysium-project.net:6666josh.elysium-project.net:7777erick.elysium-project.net:8888
Or if you wanted to connect to the 'production' instance,
elysium-project.net:4444
Where 6666,7777,8888, and 4444 are examples. We can decide as a group the actual port numbers we want to use for various environment builds.
Client application should attempt to automatically make a connection to the server on startup.
Be aware that each vhost should run it's own server application instance, and each vhost should claim a port number. This means the server connection details should be configurable for the client. Whether this is done in code, or read from a configuration file doesn't matter.
For instance, if you wanted to connect to your local server instance if you are testing server code changes, you would connect to the subdomain and portname you claim.
nick.elysium-project.net:6666josh.elysium-project.net:7777erick.elysium-project.net:8888Or if you wanted to connect to the 'production' instance,
elysium-project.net:4444Where 6666,7777,8888, and 4444 are examples. We can decide as a group the actual port numbers we want to use for various environment builds.