| 1 |
Java Calls (mainly Interfaces and not methods) to capabilities expressed in implementation neutral form
|
| 2 |
Drivers convert these general calls to vendor specific implementation of service
|
| 3 |
Java code can either be all on client (2-tier) or on client and middle tier (3 tier)
|
| 4 |
e.g. JDBC is a universal interface to all relational databases
|
| 5 |
Adoption of this JDBC implies that vendor specific solutions (such as Oracle's PL/SQL) are immediately less attractive
-
Oracle must however support JDBC and de-emphasize PL/SQL because of importance of "seamless" interfaces!
|
| 6 |
Note database business is larger than simulation business
-
Maybe "computing" too small a field to get such agreements!
|
