Setting tomcat_ip configuration parameter to 0.0.0.0 causes browser open failure

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Change the value of the tomcat_ip parameter to 0.0.0.0 so that other systems 
in your LAN can access DsBudget

2.  Click the desktop icon to start DsBudget or use the "Open dsBudget" option 
from the TaskBar menu to open DsBudget in a browser.

3. Browser attempts to open http://0.0.0.0:16091/dsbudget/main and fails as 
this is not a valid IP address for localhost.

What is the expected output? The DsBudget main page

What do you see instead?  An error message (browser specific content) 
indicating the page cannot be loaded.

What version of the product are you using? On what operating system?
2.0.24

Please provide any additional information below.

Original issue reported on code.google.com by lync...@gmail.com on 10 Oct 2013 at 11:05

[GoogleCodeExporter]

Humm. I might need to change the instruction for this.

Instead of using 0.0.0.0, find the IP address of your computer that you are 
using as a server (on Windows, run "cmd", then type "ipconfig" and look for 
IPv4 address.

So, on my case, I did 

tomcat_ip = 192.168.1.77
tomcat_port = 16091

Then, I can access the dsbudget server from anywhere in the LAN via
> http://192.168.1.77:16091/dsbudget/main

However, I recommend using shared file system to share BudgetDocument.xml and 
run dsBudget server/client on each machine, instead of trying to share a single 
server .. although either method should work for the most part..

Original comment by soichih on 11 Oct 2013 at 1:48

• Changed state: Done

[GoogleCodeExporter]

I would think two applications operating on the same data file would encounter 
concurrency issues.  Why do you suggest this approach over a single application 
available to multiple clients?

Original comment by lync...@gmail.com on 12 Oct 2013 at 11:03

[GoogleCodeExporter]

dsBudget checks to make sure that BudgetDocument.xml was not modified by 
outside problem, so unless 2 users accessing dsBudget on 2 locations at the 
same time, it should be fine.

Meanwhile, accessing the same server from 2 clients should work fine but it's 
not tested as much as accessing the same document from the same server. Like I 
said, either method should work fine, but please let me know if you encounter 
any issues.

Original comment by soichih on 13 Oct 2013 at 5:02