1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
|
Description: Fix spelling errors in manpage
Origin: vendor
Author: Salvatore Bonaccorso <carnil@debian.org>
Last-Update: 2016-05-11
Forwarded: https://rt.cpan.org/Ticket/Display.html?id=114315
Bug: https://rt.cpan.org/Ticket/Display.html?id=114315
--- a/lib/RPC/XML/Client.pm
+++ b/lib/RPC/XML/Client.pm
@@ -124,7 +124,7 @@ sub new
# Parameters to control the point at which messages are shunted to temp
# files due to size, and where to home the temp files. Start with a size
- # threshhold of 1Meg and no specific dir (which will fall-through to the
+ # threshold of 1Meg and no specific dir (which will fall-through to the
# tmpdir() method of File::Spec).
$self->{__message_file_thresh} = $attrs{message_file_thresh} || 1_048_576;
$self->{__message_temp_dir} = $attrs{message_temp_dir} || q{};
@@ -259,7 +259,7 @@ sub send_request ## no critic (ProhibitE
}
# Next step, determine our content's disposition. If it is above the
- # threshhold for a requested file cut-off, send it to a temp file and use
+ # threshold for a requested file cut-off, send it to a temp file and use
# a closure on the request object to manage content.
if ($self->message_file_thresh and
$self->message_file_thresh <= $req->length)
@@ -528,7 +528,7 @@ BEGIN
}
}
-# Fetch/set the compression threshhold
+# Fetch/set the compression threshold
sub compress_thresh
{
my $self = shift;
@@ -723,7 +723,7 @@ would be larger than this when stringifi
temporary file, and spooled from there instead. This is useful for cases in
which the request includes B<RPC::XML::base64> objects that are themselves
spooled from file-handles. This test is independent of compression, so even
-if compression of a request would drop it below this threshhold, it will be
+if compression of a request would drop it below this threshold, it will be
spooled anyway. The file itself is created via File::Temp with UNLINK=>1,
so once it is freed the disk space is immediately freed.
@@ -839,11 +839,11 @@ are not compressed by default.
If a client is communicating with a server that is known to support compressed
messages, this method can be used to tell the client object to compress any
-outgoing messages that are longer than the threshhold setting in bytes.
+outgoing messages that are longer than the threshold setting in bytes.
=item compress_thresh([MIN_LIMIT])
-With no arguments, returns the current compression threshhold; messages
+With no arguments, returns the current compression threshold; messages
smaller than this number of bytes will not be compressed, regardless of the
above method setting. If a number is passed, this is set to the new
lower-limit. The default value is 4096 (4k).
--- a/lib/RPC/XML/Procedure.pm
+++ b/lib/RPC/XML/Procedure.pm
@@ -868,7 +868,7 @@ arguments to the constructor are variabl
If there is exactly on argument that is not a reference, it is assumed to be a
filename from which the method is to be loaded. This is presumed to be in the
-B<XPL> format descibed below (see L</"XPL File Structure">). If the file
+B<XPL> format described below (see L</"XPL File Structure">). If the file
cannot be opened, or if once opened cannot be parsed, an error is raised.
=item HASHREF
--- a/lib/RPC/XML/Server.pm
+++ b/lib/RPC/XML/Server.pm
@@ -249,7 +249,7 @@ sub new ## no critic (ProhibitExcessComp
# Parameters to control the point at which messages are shunted to temp
# files due to size, and where to home the temp files. Start with a size
- # threshhold of 1Meg and no specific dir (which will fall-through to the
+ # threshold of 1Meg and no specific dir (which will fall-through to the
# tmpdir() method of File::Spec).
$self->{__message_file_thresh} = delete $args{message_file_thresh} ||
1_048_576;
@@ -1011,7 +1011,7 @@ sub process_request ## no critic (Prohib
$resp->header(Content_Encoding => $self->compress);
}
# Next step, determine the response disposition. If it is above the
- # threshhold for a requested file cut-off, send it to a temp file
+ # threshold for a requested file cut-off, send it to a temp file
if ($self->message_file_thresh &&
$self->message_file_thresh < $respxml->length)
{
@@ -1846,7 +1846,7 @@ would be larger than this when stringifi
temporary file, and spooled from there instead. This is useful for cases in
which the request includes B<RPC::XML::base64> objects that are themselves
spooled from file-handles. This test is independent of compression, so even
-if compression of a request would drop it below this threshhold, it will be
+if compression of a request would drop it below this threshold, it will be
spooled anyway. The file itself is created via File::Temp with C<UNLINK> set,
so once it is freed the disk space is immediately freed.
@@ -2165,7 +2165,7 @@ The calling server object shares the met
B<NAMES> with the source-server passed as the first object. The source must
derive from this package in order for this operation to be permitted. At least
one method must be specified, and all are specified by name (not by object
-refernce). Both objects will reference the same exact B<RPC::XML::Procedure>
+reference). Both objects will reference the same exact B<RPC::XML::Procedure>
(or derivative thereof) object in this case, meaning that call-statistics and
the like will reflect the combined data. If one or more of the passed names are
not present on the source server, an error message is returned and none are
@@ -2419,8 +2419,8 @@ implements these, their help files and o
The B<RPC::XML::Server> class now supports compressed messages, both incoming
and outgoing. If a client indicates that it can understand compressed content,
the server will use the B<Compress::Zlib> (available from CPAN) module, if
-available, to compress any outgoing messages above a certain threshhold in
-size (the default threshhold is set to 4096 bytes). The following methods are
+available, to compress any outgoing messages above a certain threshold in
+size (the default threshold is set to 4096 bytes). The following methods are
all related to the compression support within the server class:
=over 4
@@ -2433,7 +2433,7 @@ time, and cannot be changed.
=item compress_thresh([MIN_LIMIT])
-Return or set the compression threshhold value. Messages smaller than this
+Return or set the compression threshold value. Messages smaller than this
size in bytes will not be compressed, even when compression is available, to
save on CPU resources. If a value is passed, it becomes the new limit and the
old value is returned.
@@ -2445,7 +2445,7 @@ old value is returned.
If the server anticipates handling large out-bound messages (for example, if
the hosted code returns large Base64 values pre-encoded from file handles),
the C<message_file_thresh> and C<message_temp_dir> settings may be used in a
-manner similar to B<RPC::XML::Client>. Specifically, the threshhold is used to
+manner similar to B<RPC::XML::Client>. Specifically, the threshold is used to
determine when a message should be spooled to a filehandle rather than made
into an in-memory string (the B<RPC::XML::base64> type can use a filehandle,
thus eliminating the need for the data to ever be completely in memory). An
@@ -2454,7 +2454,7 @@ anonymous temporary file is used for the
Note that the message size is checked before compression is applied, since the
size of the compressed output cannot be known until the full message is
examined. It is possible that a message will be spooled even if its compressed
-size is below the threshhold, if the uncompressed size exceeds the threshhold.
+size is below the threshold, if the uncompressed size exceeds the threshold.
=over 4
|
