This week's book giveaway is in the Agile and other Processes forum. We're giving away four copies of The Mikado Method and have Ola Ellnestam and Daniel Brolund on-line! See this thread for details.
My application reads (doesn't write) a few tables from a database, using JDBC for simple queries and a little MetaData retrieval. But, now I need to distribute the application to others, and I want: 1) trivial setup for them (e.g., no separate install of a database product) 2) hidden database data (I don't need top level security, but I at least want them to work if they're going to look at it) 3) minimal changes to my current application One solution might be to somehow copy the data into Java classes, and use a JDBC driver that would access this class-based database. Just having the data in classes (they wouldn't see the source) would be enough 'data hiding' for my purposes. A second solution would be to use a simple database whose software was entirely in Java classes, but whose data was in one or more files. The data would have to be reasonably hidden through some type of encryption. Seems to me like others must have had similar needs over time. I'd like to hear about any ready-made solutions to my need. Or, if you can point me to any Java source that I might use as a starting point, would help, too. Thanks, Ron (ron@emergentweb.com)
matt hooker
Ranch Hand
Joined: Jul 26, 2001
Posts: 46
posted
0
Mmm, interesting. I would look to store the data in some sort of java datastore .. maybe a set of serialized hashes or somesuch. Maybe even create MD5 hashes or somesuch of the data and then 'de-hash' the data when it is retrieved .. that would be fun eh ? Have fun.
Its not what you do, its the way you say you've done it.
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to
run our stuff on 16 servers instead of 3.
0
