1SOAP::Constants(3) User Contributed Perl Documentation SOAP::Constants(3)
2
3
4
6 SOAP::Constants - SOAP::Lite provides several variables to allows pro‐
7 grammers and users to modify the behavior of SOAP::Lite in specific
8 ways.
9
11 A number of "constant" values are provided by means of this namespace.
12 The values aren't constants in the strictest sense; the purpose of the
13 values detailed here is to allow the application to change them if it
14 desires to alter the specific behavior governed.
15
17 $DO_NOT_USE_XML_PARSER
18
19 The SOAP::Lite package attempts to locate and use the XML::Parser pack‐
20 age, falling back on an internal, pure-Perl parser in its absence. This
21 package is a fast parser, based on the Expat parser developed by James
22 Clark. If the application sets this value to 1, there will be no
23 attempt to locate or use XML::Parser. There are several reasons you
24 might choose to do this. If the package will never be made available,
25 there is no reason to perform the test. Setting this parameter is less
26 time-consuming than the test for the package would be. Also, the
27 XML::Parser code links against the Expat libraries for the C language.
28 In some environments, this could cause a problem when mixed with other
29 applications that may be linked against a different version of the same
30 libraries. This was once the case with certain combinations of Apache,
31 mod_perl and XML::Parser.
32
33 $DO_NOT_USE_CHARSET
34
35 Unless this parameter is set to 1, outgoing Content-Type headers will
36 include specification of the character set used in encoding the message
37 itself. Not all endpoints (client or server) may be able to properly
38 deal with that data on the content header, however. If dealing with an
39 endpoint that expects to do a more literal examination of the header as
40 whole (as opposed to fully parsing it), this parameter may prove use‐
41 ful.
42
43 $DO_NOT_CHECK_CONTENT_TYPE
44
45 The content-type itself for a SOAP message is rather clearly defined,
46 and in most cases, an application would have no reason to disable the
47 testing of that header. This having been said, the content-type for
48 SOAP 1.2 is still only a recommended draft, and badly coded endpoints
49 might send valid messages with invalid Content-Type headers. While the
50 "right" thing to do would be to reject such messages, that isn't always
51 an option. Setting this parameter to 1 allows the toolkit to skip the
52 content-type test.
53
54 $PATCH_HTTP_KEEPALIVE
55
56 SOAP::Lite's HTTP Transport module attempts to provide a simple patch
57 to LWP::Protocol to enable HTTP Keep Alive. By default, this patch is
58 turned off, if however you would like to turn on the experimental patch
59 change the constant like so:
60
61 $SOAP::Constants::PATCH_HTTP_KEEPALIVE = 1;
62
64 Special thanks to O'Reilly publishing which has graciously allowed
65 SOAP::Lite to republish and redistribute large excerpts from Program‐
66 ming Web Services with Perl, mainly the SOAP::Lite reference found in
67 Appendix B.
68
70 Copyright (C) 2000-2004 Paul Kulchenko. All rights reserved.
71
72 This library is free software; you can redistribute it and/or modify it
73 under the same terms as Perl itself.
74
76 Paul Kulchenko (paulclinger@yahoo.com)
77
78 Randy J. Ray (rjray@blackperl.com)
79
80 Byrne Reese (byrne@majordojo.com)
81
82
83
84perl v5.8.8 2006-06-15 SOAP::Constants(3)