8.1 Choosing a Protocol


Deciding which protocol to use is generally easy; HTTP is a de facto standard in most web-enabled environments. However, there are protocols, some older than HTTP and some newer , that can be very effective at managing SOAP traffic. Some of the protocols discussed in this chapter are a natural fit. Jabber, for example, is already based upon XML. Having a server that reads requests from an email account using POP3 lets any application that can send mail become a client.

It may also help to look at the protocols in this chapter not as replacements for HTTP but as additions to a set of solutions that include HTTP. With the spread of new devices and platforms, flexibility is more a requirement and less a luxury than it used to be.

The important factors in evaluating the alternatives presented in this chapter are how the tools can work to solve the problems you face. A server that tends to receive requests that don't require immediate response (such as a web service for managing mailing lists) can use POP3 to monitor email requests (such as subscribe and unsubscribe). The Jabber instant messaging protocol is growing in acceptance, and the design allows you to design applications other than just chat clients . There are cases in which TCP/IP is a better choice than HTTP. The goal isn't to justify each of the different protocols but rather to show how to use them if the application design calls for it.



Programming Web Services with Perl
Programming Web Services with Perl
ISBN: 0596002068
EAN: 2147483647
Year: 2000
Pages: 123

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net