Gytis,
is it worth to waste time by implementing gui configuration persistence (window size and location, columns order etc.)? currenlty I store only database file path, host name and port (different for each mode) - is it enough (for this assignment only, since I'm sure that this couldn't be enough for real application)?
As I tend to say a lot in my replies:- These problems are design decisions that you have to make and document your reasoning. Some people will store window size and location etc. You could simply make window size a fixed percentage of screen size and always centered. You decide but persist what they ask you to persist - no point going over spec!
how to handle situation, then server and client applications are started in the same machine from the same folder - only one of them will get properties saved? I could implement some kind of refresh-before-save for Properties, but event with this approach there is no possibility to synchronize different VMs for properties file access? maybe I just need to mention this problem in choices and userguide (do not use networked mode for single workstation)?
One property file can have more than 3 variables. eg. ServerFile, LocalFile, ServerHost, NetworkHost, ...
Steven