Re: informix universal server java api

Sveinn Sveinsson wrote: > > Eric McDermid wrote: > > > > > JOI is actually a single API with two different implementations. The > > one you are apparently using is the "direct" API, which is built atop > > the Informix C API (libdmi and ESQL/C). That's why you need to add > > something to your LD_LIBRARY_PATH. > > > > If you need a Java-only solution (as in the case of applets), you'll > > want to use the "remoted" implementation of JOI. The remoted implementation > > uses RMI to communicate from the client to a dedicated middle tier > > running the direct implementation. > > > > > > > -- Eric > > > > -------------- > > Eric McDermid > > Principal Software Engineer, Java Development Tools > > Informix Software, Inc. > > (posting from a personal account) > > But why doesn't Informix implement a pure Java version of JOI? > > I can't see why you have to implement part of the connectivity > in C, since Java has all the necessary facilities to communicate > directly with the database engine through the sqlexec socket. > > Then the RMI version of JOI could be implemented on top of this > pure java connectivity. > I think that is exactly what Eric was saying. For tcp/ip socket connection, you can use a java only solution. However, if you want to connect via shared memory, (server side connection), you need the esql/c libs. Right? -Mikey -- #include <std_disclaimer.h> /* Mike Segel (MS385) */ #include <No_Spam.h> #ifdef OFFENDED_BY_CONTENT The author takes no responsibility for this post. Any resemblence to a coherent rational thought is purely coincidence. -The Management. #endif ***************************** Due to AGIS's Refusal to Act Responsibly We are blocking all of their domains at the packet level. This block will exist until AGIS modifies their policies to conform to existing RFCs and net community standards. We encourage all ISPs and domain holders to do the same. *****************************