Barrett

Greenhorn
+ Follow
since Jan 14, 2002
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Barrett

You might want to consider keeping all of the database access code on the middle, or server tier. This way it will be self contained and should be easier to administer and maintain.
You could communicate with your server using RMI. I'm not sure I understand your question about RMI vs JDBC. Even if you use RMI you will still need JDBC to communicate with your DB, so it doesn't seem like an 'either/or' situation, but maybe I'm missing something.
It may, or may not be a concern. That depends on your application.
Here's a scenario to consider: 2 people read the same data from the database. Person #1 updates the data. Person #2 has no way to know that the data has been updated. Now person #2 submits their update. This wipes out person #1's changes.
If it's highly unlikely that a situation like this can occur it may not be worth worrying about. Depending on the type of application you are writing, it may or may not be an issue.