A couple of comments on the open source licensing and Java APIs –
- I’m looking into relicensing RTL, JOARSE, and COARSE under the LGPL. I would like to leave the ROI project as GPL. I should have a decision on this by the end of the day today. - This is just my personal preference, but faced with the choice of two different JNI layers on top of a commercial native library, I’ll pick the one with source code available if it is high quality. (And you’ll see that the implementation of the JNI layer for JOARSE is fairly trivial). That’s just my personal preference, of course. You might instead prefer one that is closed-source but commercially supported. - The only practical way I see to get to a “pure” Java API is to build a server component that itself uses JNI, and then have the pure Java client API talk to this service instead of the AR Server. You’d have to install this proxy/adapter software on the server box, and the client Java API would communicate with HTTP(s). This is certainly doable, but I have not spent any time on it myself. There is proprietary stuff inside the C API that makes it impossible to build a pure Java API yourself – but you can choose whether to put the JNI bit on every client, or on this server component. Regards, Dan Hardy Pathworks Software http://www.PathworksSoftware.com/ __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
