Centera SDK under Mac OS X

What a shame, I was really looking forward to getting rid of my VMWare:(

Just for interest: what was the reason behind providing the SDK as Java over JNI? Normally

I do this only when running against native applications on the same host, connecting to remote

system per TCP should not need JNI to be involved.

  c

Using JNI allows us to write just one SDK and then just wrap it for use in Java.

Guys anyone else got a better answer to this simplistic although basically correct one?

Hmmm, I guess writing an SDK in plain C/C++ involves porting it to every platform seperately which is normally lots of overhead.

I don't know which mechanism the Centera SDK uses to communicate with the server, but if its just TCP/IP then it would

be easier to do it all in Java, you would just need one implementation for all platforms

Christoph - virtually all languages allow for calling low-level library routines written in C. If the SDK was writtent in Java, it would be unusable by most languages and rule out it's use by the large majority of ISV partner applications (as they are not Java based).

Hi, thats a good point, I thought that it would be the other way round: Java the normal approach and native applications the special case. That

way it makes perfect sense.

From my side Java would be nicer (because than there would be no problem using it on Mac OS X) but I understand that you must have the majority

of customers in mind:)

Many thanks for the information!

  c

I thought that the Centera SDK's Java API was in fact layered on top of a C library.  From the manual:

"The SDK consists of both a C and Java API. The Java API is built upon

the C API via a Java Native Interface (JNI) layer."

So much for Java running everywhere!

Thats right, it is just like explained in the  comment above. The problem here is not within the Java parts, its just that they didn't port their C++

library to Mac OS X. I guess the porting would not be that much of a problem as its a really small library, its probably more a matter of

supporting it.

  c

P.S. yes, its really a shame and I guess a Java-only port of this library would be a matter of 1-2 months work and would help many developers