This page shows how to create an Ice client application with MATLAB.
On this page:
Compiling a Slice Definition for MATLAB
The first step in creating our MATLAB application is to compile our Slice definition to generate MATLAB proxies. You can compile the definition as follows:
slice2matlab compiler produces a single source file,
Printer.m, from this definition. The exact contents of the source file do not concern us for now — it contains the generated code that corresponds to the
Printer interface we defined in
Writing a Client in MATLAB
The client code, in
client.m, is shown below in full:
The function goes through the following steps:
- We check whether the Ice library is loaded and call
loadlibraryif necessary. The
'ice'argument is the name of the Ice for MATLAB library, while
@iceprotodenotes a prototype file. This file,
iceproto.m, is included in the Ice for MATLAB distribution. Using a prototype file is simpler and more efficient than a header file because it avoids the need for MATLAB to run a C compiler to preprocess a header file.
- We initialize the Ice run time by calling
Ice.initialize. The call to
Ice.Communicatorreference, which is the main object in the Ice run time.
- We register a "clean up" function that will be called when the
cleanupvariable is reclaimed and ensures that the communicator is destroyed before the program terminates. Doing this is essential in order to correctly finalize the Ice run time: the program must call
destroyon any communicator it has created; otherwise, undefined behavior results.
- The next step is to obtain a proxy for the remote printer. We create a proxy by calling
stringToProxyon the communicator, with the string
'SimplePrinter:default -p 10000'. Note that the string contains the object identity and the port number that were used by the server. (Obviously, hard-coding object identities and port numbers into our applications is a bad idea, but it will do for now; we will see more architecturally sound ways of doing this when we discuss IceGrid.)
- The proxy returned by
stringToProxyis of type
Ice.ObjectPrx, which is at the root of the inheritance tree for interfaces. But to actually talk to our printer, we need a proxy for a
Demo::Printerinterface, not an
Objectinterface. To do this, we need to do a down-cast by calling
Demo.PrinterPrx.checkedCast. A checked cast sends a message to the server, effectively asking "is this a proxy for a
Demo::Printerinterface?" If so, the call returns a proxy of type
Demo.PrinterPrx; otherwise, if the proxy denotes an interface of some other type, the call returns an empty array.
- We test that the down-cast succeeded and, if not, throw an exception that terminates the client.
- We now have a live proxy in our address space and can call the
printStringmethod, passing it the time-honored
'Hello World!'string. The server prints that string on its terminal.
Running the Client in MATLAB
The server must be started before the client. Since Ice for MATLAB does not support server-side behavior, we need to use a server from another language mapping. In this case, we will use the C++ server:
At this point, we won't see anything because the server simply waits for a client to connect to it. We run the client in a MATLAB console:
The client runs and exits without producing any output; however, in the server window, we see the
"Hello World!" message that is produced by the printer. To get rid of the server, we interrupt it on the command line.
If anything goes wrong, the client will print an error message. For example, if we run the client without having first started the server, we get something like the following:
Note that, to successfully run the client, MATLAB must be able to locate Ice for MATLAB. See the Ice for MATLAB installation instructions for more information.