Relationship with the Native C Client

This version also includes the Native C Client, a full C implementation of WebSphere MQ Everyplace. While the C Bindings and the Native C Client share the API header files, there are some differences. These are documented in WebSphere MQ Everyplace C Programming Guide for Palm OS.

One difference is that, in the C Bindings, you must set the #define BINDINGS preprocessor definition before including the MQe_API.h header file. Also, the libraries that are linked have slightly different names.

The Native C Client and the C Bindings complement eachother, in that the Native C Client is for devices like Pocket PCs, while the C Bindings is supported on Windows platforms. The Native C Client does not include server functionality. Therefore, in a complete solution, it will need to use a server written using either using the Java code base or the C Bindings.



© IBM Corporation 2000, 2003. All Rights Reserved