Porting the Sample Code to the iPhone
The process of porting the sample code from the book to the iPhone highlights some of the unique features of the iPhone. In particular, some of the unique features of the development environment include:

• The use of Objective C
• The process of creating an EGL rendering context using the EAGLContext.
• Detection of device capabilities and creating an OpenGL ES 2.0 context
• The use of a framebuffer object as the primary rendering surface

Once you have created and setup a rendering context, programming with OpenGL ES 2.0 on the iPhone is identical to any other platform. However, there are some unique aspects of the platform that are worth understanding before jumping into the code.

Building Web Services with JAX-WS

JAX-WS stands for Java API for XML Web Services. JAX-WS is a technology for building web services and clients that communicate using XML. JAX-WS allows developers to write message-oriented as well as RPC-oriented web services. In JAX-WS, a remote procedure call is represented by an XML-based protocol such as SOAP. The SOAP specification defines the envelope structure, encoding rules, and conventions for representing remote procedure calls and responses. These calls and responses are transmitted as SOAP messages (XML files) over HTTP.

Although SOAP messages are complex, the JAX-WS API hides this complexity from the application developer. On the server side, the developer specifies the remote procedures by defining methods in an interface written in the Java programming language. The developer also codes one or more classes that implement those methods. Client programs are also easy to code. A client creates a proxy (a local object representing the service) and then simply invokes methods on the proxy. With JAX-WS, the developer does not generate or parse SOAP messages. It is the JAX-WS runtime system that converts the API calls and responses to and from SOAP messages.

The iPhone SDK provides the tools and resources needed to create native iPhone applications that appear as icons on the user’s Home screen. Unlike a web application, which runs in Safari, a native application runs directly as a standalone executable on an iPhone OS–based device. Native applications have access to all the features that make the iPhone and iPod touch interesting, such as the accelerometers, location service, and Multi-Touch interface. They can also save data to the local file system and even communicate with other installed applications through custom URL schemes.

In iPhone OS, you develop native applications using the UIKit framework. This framework provides fundamental infrastructure and default behavior that makes it possible to create a functional application in a matter of minutes. Even though the UIKit framework (and other frameworks on the system) provide a significant amount of default behavior, they also provide hooks that you can use to customize and extend that behavior.

Learn how to integrate iPhone and iPod touch with your enterprise systems.
This guide is for system administrators. It provides information about deploying and supporting iPhone and iPod touch in enterprise environments.

What’s New for the Enterprise in iPhone OS 3.0 and Later
iPhone OS 3.x includes numerous enhancements, including the following items of special interest to enterprise users.

• CalDAV calendar wireless syncing is now supported.
• LDAP server support for contact look-up in mail, address book, and SMS.
• Configuration profiles can be encrypted and locked to a device so that their removal requires an administrative password.
• iPhone Configuration Utility now allows you to add and remove encrypted configuration profiles directly onto devices that are connected to your computer by USB.
• Online Certificate Status Protocol (OCSP) is now supported for certificate revocation.
• On-demand certificate-based VPN connections are now supported.