November 2007
Intermediate to advanced
928 pages
26h 9m
English
How much easier our lives as developers would be if we never encountered erroneous conditions! Bad or missing input, data, hardware, assumptions, and a myriad of other conditions can cause untold grief. This is especially true if your code is not designed to handle such conditions properly. Microsoft Exchange Server 2007 Web Services (EWS) must also deal with error conditions. Being an application programming interface (API), in most cases Exchange Web Services reports these conditions to you, the caller. This chapter is all about how these conditions are reported and what you can do about them.
Because Exchange Web Services is a standards-based Web service, all Exchange Web Services requests ...