This page shows how to create an Ice client application with PHP.
On this page:
Compiling a Slice Definition for PHP
The first step in creating our PHP application is to compile our Slice definition to generate PHP code. You can compile the definition as follows:
slice2php compiler produces a single source file,
Printer.php, 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 PHP
The client code, in
Client.php, is shown below in full:
The program begins with
require statements to load the Ice run-time definitions (
Ice.php) and the code we generated from our Slice definition in the previous section (
The body of the main program contains a
try block in which we place all the client code, followed by a
catch block. The
catch block catches all exceptions that may be thrown by the code; the intent is that, if the code encounters an unexpected run-time exception anywhere, the stack is unwound all the way back to the main program, which prints the exception and then returns failure to the operating system.
The body of our
try block goes through the following steps:
- 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.
- 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 and classes. 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\PrinterPrxHelper::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 narrowed to the
Printerinterface; otherwise, if the proxy denotes an interface of some other type, the call returns
- 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.
Before the code exits, it destroys the communicator (if one was created successfully). Doing this is essential in order to correctly finalize the Ice run time. If a script neglects to destroy the communicator, Ice destroys it automatically.
Running the Client in PHP
The server must be started before the client. Since Ice for PHP 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 different window using PHP's command-line interpreter:
The client runs and exits without producing any output; however, in the server window, we see the
"Hello World!" 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, the PHP interpreter must be able to locate the Ice extension for PHP. See the Ice for PHP installation instructions for more information.