1SOAP::Constants(3)    User Contributed Perl Documentation   SOAP::Constants(3)
2
3
4

NAME

6       SOAP::Constants - SOAP::Lite provides several variables to allows
7       programmers and users to modify the behavior of SOAP::Lite in specific
8       ways.
9

DESCRIPTION

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

CONSTANTS

17   $DO_NOT_USE_XML_PARSER
18       The SOAP::Lite package attempts to locate and use the XML::Parser
19       package, falling back on an internal, pure-Perl parser in its absence.
20       This package is a fast parser, based on the Expat parser developed by
21       James Clark. If the application sets this value to 1, there will be no
22       attempt to locate or use XML::Parser. There are several reasons you
23       might choose to do this. If the package will never be made available,
24       there is no reason to perform the test. Setting this parameter is less
25       time-consuming than the test for the package would be. Also, the
26       XML::Parser code links against the Expat libraries for the C language.
27       In some environments, this could cause a problem when mixed with other
28       applications that may be linked against a different version of the same
29       libraries. This was once the case with certain combinations of Apache,
30       mod_perl and XML::Parser.
31
32   $DO_NOT_USE_CHARSET
33       Unless this parameter is set to 1, outgoing Content-Type headers will
34       include specification of the character set used in encoding the message
35       itself. Not all endpoints (client or server) may be able to properly
36       deal with that data on the content header, however. If dealing with an
37       endpoint that expects to do a more literal examination of the header as
38       whole (as opposed to fully parsing it), this parameter may prove
39       useful.
40
41   $DO_NOT_CHECK_CONTENT_TYPE
42       The content-type itself for a SOAP message is rather clearly defined,
43       and in most cases, an application would have no reason to disable the
44       testing of that header. This having been said, the content-type for
45       SOAP 1.2 is still only a recommended draft, and badly coded endpoints
46       might send valid messages with invalid Content-Type headers. While the
47       "right" thing to do would be to reject such messages, that isn't always
48       an option. Setting this parameter to 1 allows the toolkit to skip the
49       content-type test.
50
51   $PATCH_HTTP_KEEPALIVE
52       SOAP::Lite's HTTP Transport module attempts to provide a simple patch
53       to LWP::Protocol to enable HTTP Keep Alive. By default, this patch is
54       turned off, if however you would like to turn on the experimental patch
55       change the constant like so:
56
57         $SOAP::Constants::PATCH_HTTP_KEEPALIVE = 1;
58

ACKNOWLEDGEMENTS

60       Special thanks to O'Reilly publishing which has graciously allowed
61       SOAP::Lite to republish and redistribute large excerpts from
62       Programming Web Services with Perl, mainly the SOAP::Lite reference
63       found in Appendix B.
64
66       Copyright (C) 2000-2004 Paul Kulchenko. All rights reserved.
67
68       This library is free software; you can redistribute it and/or modify it
69       under the same terms as Perl itself.
70

AUTHORS

72       Paul Kulchenko (paulclinger@yahoo.com)
73
74       Randy J. Ray (rjray@blackperl.com)
75
76       Byrne Reese (byrne@majordojo.com)
77
78
79
80perl v5.36.0                      2023-01-20                SOAP::Constants(3)
Impressum