Hi Diego,
I'm a little dense in this area, can you break down the components? I'm thinking that
I'll
have to write my own software on the server side to be able to select data as well as
do
the normal I/O. While UniData does have a C adapter so that I can access the data files
from Unix I'm not sure what else that I would have to write to complete the chain.
Is JNI (Java Network Interface)? Just guessing. That's a new one for me.
Am I on the right track?
Thanks,
Andrew (learning Java for one week so far)
Diego Pons wrote:
> Andrew McLaughlin wrote:
> >
> > Is anyone working with RMI so far? I'm launching into a project where I'll try to
> > connect Sanfrancisco to a legacy database (UniData). While UniData does provide
>ODBC
> > it's too slow and, gulp, read-only.
> >
> > I welcome any and all commentary with open arms and squinted eyes!!
> >
>
> I'm using RMI in a project integrating a legacy RPC system with Java clients.
> It works very well and I do not see any significant performance degradation
> compared to regular RPC connections.
>
> If you decide to use JNI to interface directly to your legacy API, try very
> hard to centralize the API into a single JNI call (ioctl-like). It is very
> tedious and error-prone to develop JNI interface calls.
> It took +50 lines of the ugliest C code per each argument/call.
>
> --
> Diego Pons Pharos Consulting LLC
--
Andrew McLaughlin
Manager, Applications Software Development
People 1st Technology Group, Inc.
http://www.people-1st.com
714/668-7151
