Re: JDBC: bottom line
Hi Matt, Matt Taylor <mtaylor@transport.com> wrote in article <01bc34c7$dbc22000$d17a02c7@Matt.acbc.com>... > I've looked through the pages of what I thought were the most prominent > driver writers - OpenLink and Intersolv - and I don't see just a single > driver for the products I want - which are MS SQL-Server 6.5 on Windows NT > 4.0 and Progress V7 running on SCO Unix Open Server 5.0. > OpenLink Software has a Thin (45K in size) Generic High-Performance JDBC Driver (written in Java without native methods) that supports : MS SQL Server (4.x, 6.x) , Progress (V6/7/8), CA-Ingres, PostgresSQL, Unify 2000, DB2, Informix (5/6/7). Simply visit http://www.openlinksw.com To download and experience the potential of JDBC !!!! OpenLink Software will also be unleashing (at JavaOne in San Francisco, commercial release in 14 days after Expo) an extension to the ResultSet Object that supports Bi-Directional Scrolling, Advanced Concurrency, and Isolation control. This extension will be freely available to all Java/JDBC developers at no cost, this is a 100% Java implementation, thus where ever there is a Java (1.02 or 1.1) VM this will work. In addition to this our WebJDBC classes make this JDBC enhancement independent of Web Browser from an Applet development perspective. > Am I just missing something here, or does it seem like everyone is avoiding > SQL-Server 6.5/NT 4.0 (wouldn't this be a nice way to co-opt MS for once, > instead of the other way aoround), and that you have to buy a lot of other > crap (interface through their development environment or their general > driver technology developed for ODBC, etc.). So far it's maddening. I'm > totally flattened that vendors of database engines other than IBM, Oracle > and Sybase don't seem to have developed relationships with any good drivers > companies to get JDBC going now. > OpenLink has delivered first class, sophisticated high-performance data access drivers for years, the only issue is how many of the awesome developers out there know this (its amazing how many experts/analysts/pundits/ develop amnesia when its time to refer wondering data access souls to OpenLink, for instance we have an ODBC and a JDBC Driver for PostgresSQL (used to be known as Postgres95) a sophisticated Object-Relational DBMS engine (http://www.postgresql.org ) it is free of charge as well (in source and binary formats), it also runs on Linux/BSDI/FreeBSD/NetBSD/MKLinux and other free or lost cost but powerful server environments, how many people know that ??? OpenLink's JDBC Drivers are not inextricably linked with ODBC as the strangely popular JDBC-ODBC bridge drivers are (or should I say mangled with ODBC, ODBC has its place but not in an operating system independent world without our UDBC implementation). Our Drivers will use ODBC on NT servers (not the case under UNIX or VMS) but this is simply because ODBC is native to NT, more importantly though the bridging takes place on the Server. > Maybe it's just me, but it appears that the best performance and > wonderfulness with Java right now could be gotten by a simple TCP/IP Java > application to Java server program using either Sockets/ServerSockets or > RMI for a client/server connection. OpenLink delivers the kind of performance your refer to via JDBC already. >You could easily build your own Java > programs to go between the Java application and server besides JDBC. A > threaded ServerSocket program which just listened for requests and passed > them onto anther program with a different thread and went back to listening > (a sort of TP monitering Socket), or a RMI server program which could be > called by any number of clients. The TP monitor socket could always pass > on the remote application's info to any of a group of identical programs > bound to a server socket on the server side which were JDBC clients. You > could do a little simple firewall/security management. > OpenLink Software has a 24/7 Virtual Laboratory accessible via the Net for all JDBC technology enthusiasts, all you have to do is download our Driver classes from our Web site and run our sample JDBC application. Once you have got this up and running you can proceed to experimenting locally by downloading our server components from our Web Site (http://www.openlinksw.com) OpenLink also has proxying capabilities that resolve the Firewall issues typically exposed when attempting (should anyone have got this far without being able to scroll backwards using the 'resultset' object ) develop JDBC based Extranet Applications or Applets. For anyone interested a detailed technical white paper on our elegant JDBC implementation is available on our Web site; http://www.openlinksw.com/docs/jdbcwp.html Java Value Proposition Recap: "Write Once & Run Anywhere" JDBC Value Proposition Recap: "Write Independent of Database Once and Run Anywhere" Do I see the word "Somewhere" anywhere in these propositions ??? May the JFORCE be with you all !!! Best Regards, Kingsley Idehen President & CEO OpenLink Software Universal Database Connectivity Technology Providers