Thomas Haws wrote: > Well, for me at least, it doesn't burst the bubble at all to speak and > plan toward a purely local package, written perhaps in Java. > Wards/troops are by definition local, and being online doesn't really > offer much other than enhanced portability and centralized backup. I > almost feel bad competing with the likes of Troopmaster and Scoutsoft, > but I guess that's what FLOSS does.
You could build a simple desktop application, but it would be inherently limited. Giving multiple people access to the same database leads to network effects and surprisingly useful capabilities. I can think of two architectures that could solve the access and security breech liability problems you guys are running into. 1. Build a networked desktop application, but put the database on a web server that can store yet not decrypt the database. People who want to access the database will need the decryption key, which the web server will not have. Even administrators of the web server will not be able to decrypt the databases. 2. Use PDA-like synchronization. If two people bring their laptops to a troop meeting, they can connect and exchange updates. The database is never stored anywhere but on individuals' laptops and desktops. The second architecture is appealing because it doesn't rely on a central server. But the first is a lot easier. Shane _______________________________________________ Ldsoss mailing list [email protected] http://lists.ldsoss.org/mailman/listinfo/ldsoss
