kXML-RPC Enables Service-Oriented Mobile Computing
Service orientation is going wireless; it's simply a matter of how much and how soon. XML-RPC and the kXML-RPC library certainly are in the mix for this inevitable convergence.
by Kyle Gabhart,
David Johnson
July 13, 2007
ervice orientation is sweeping through modern enterprise environments like the Black Plague swept through Europe (hopefully the parallels end there). At the same time, enterprises seem increasingly interested in supporting thin clients and mobile interfaces. The convergence of these trends presents new challenges and more complex requirements, which enterprise developers can help address by choosing the best messaging protocol.
A service is a platform-neutral and typically coarse-grained interface to one or more business systems that can be invoked across a network. Wireless networks complicate this invocation process because the service provider must account for dropped packets and hops across multiple relays. Consequently, wireless clients must keep their exchanges as thin as possible to ensure optimum performance. Additionally, mobile devices typically do not have an abundance of resources for processing fat requests, synchronous request-response exchanges, or storing robust data models.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!
ervice orientation is sweeping through modern enterprise environments like the Black Plague swept through Europe (hopefully the parallels end there). At the same time, enterprises seem increasingly interested in supporting thin clients and mobile interfaces. The convergence of these trends presents new challenges and more complex requirements, which enterprise developers can help address by choosing the best messaging protocol.
