aboutsummaryrefslogtreecommitdiff
path: root/doc/tcp.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/tcp.html')
-rw-r--r--doc/tcp.html697
1 files changed, 0 insertions, 697 deletions
diff --git a/doc/tcp.html b/doc/tcp.html
deleted file mode 100644
index fb627a1..0000000
--- a/doc/tcp.html
+++ /dev/null
@@ -1,697 +0,0 @@
1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
3<html>
4
5<head>
6<meta name="description" content="LuaSocket: The TCP/IP support">
7<meta name="keywords" content="Lua, LuaSocket, Socket, TCP, Library, Network, Support">
8<title>LuaSocket: TCP/IP support</title>
9<link rel="stylesheet" href="reference.css" type="text/css">
10</head>
11
12<body>
13
14<!-- header +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
15
16<div class=header>
17<hr>
18<center>
19<table summary="LuaSocket logo">
20<tr><td align=center><a href="http://www.lua.org">
21<img width=128 height=128 border=0 alt="LuaSocket" src="luasocket.png">
22</a></td></tr>
23<tr><td align=center valign=top>Network support for the Lua language
24</td></tr>
25</table>
26<p class=bar>
27<a href="index.html">home</a> &middot;
28<a href="index.html#download">download</a> &middot;
29<a href="installation.html">installation</a> &middot;
30<a href="introduction.html">introduction</a> &middot;
31<a href="reference.html">reference</a>
32</p>
33</center>
34<hr>
35</div>
36
37<!-- tcp ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
38
39<h2 id="tcp">TCP</h2>
40
41<!-- socket.tcp +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
42
43<p class=name id="socket.tcp">
44socket.<b>tcp()</b>
45</p>
46
47<p class=description>
48Creates and returns an TCP master object. A master object can
49be transformed into a server object with the method
50<a href=#listen><tt>listen</tt></a> (after a call to <a
51href=#bind><tt>bind</tt></a>) or into a client object with
52the method <a href=#connect><tt>connect</tt></a>. The only other
53method supported by a master object is the
54<a href=#close><tt>close</tt></a> method.</p>
55
56<p class=return>
57In case of success, a new master object is returned. In case of error,
58<b><tt>nil</tt></b> is returned, followed by an error message.
59</p>
60
61<p class=note>
62Note: The choice between IPv4 and IPv6 happens during a call to
63<a href=#bind><tt>bind</tt></a> or <a
64href=#bind><tt>connect</tt></a>, depending on the address
65family obtained from the resolver.
66</p>
67
68<p class=note>
69Note: Before the choice between IPv4 and IPv6 happens,
70the internal socket object is invalid and therefore <a
71href=#setoption><tt>setoption</tt></a> will fail.
72</p>
73
74<!-- socket.tcp +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
75
76<p class=name id="socket.tcp4">
77socket.<b>tcp4()</b>
78</p>
79
80<p class=description>
81Creates and returns an IPv4 TCP master object. A master object can
82be transformed into a server object with the method
83<a href=#listen><tt>listen</tt></a> (after a call to <a
84href=#bind><tt>bind</tt></a>) or into a client object with
85the method <a href=#connect><tt>connect</tt></a>. The only other
86method supported by a master object is the
87<a href=#close><tt>close</tt></a> method.</p>
88
89<p class=return>
90In case of success, a new master object is returned. In case of error,
91<b><tt>nil</tt></b> is returned, followed by an error message.
92</p>
93
94<!-- socket.tcp6 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
95
96<p class=name id="socket.tcp6">
97socket.<b>tcp6()</b>
98</p>
99
100<p class=description>
101Creates and returns an IPv6 TCP master object. A master object can
102be transformed into a server object with the method
103<a href=#listen><tt>listen</tt></a> (after a call to <a
104href=#bind><tt>bind</tt></a>) or into a client object with
105the method <a href=#connect><tt>connect</tt></a>. The only other
106method supported by a master object is the
107<a href=#close><tt>close</tt></a> method.</p>
108
109<p class=return>
110In case of success, a new master object is returned. In case of error,
111<b><tt>nil</tt></b> is returned, followed by an error message.
112</p>
113
114<p class=note>
115Note: The TCP object returned will have the option
116"<tt>ipv6-v6only</tt>" set to <tt><b>true</b></tt>.
117</p>
118
119<!-- accept +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
120
121<p class=name id="accept">
122server:<b>accept()</b>
123</p>
124
125<p class=description>
126Waits for a remote connection on the server
127object and returns a client object representing that connection.
128</p>
129
130<p class=return>
131If a connection is successfully initiated, a client object is returned.
132If a timeout condition is met, the method returns <b><tt>nil</tt></b>
133followed by the error string '<tt>timeout</tt>'. Other errors are
134reported by <b><tt>nil</tt></b> followed by a message describing the error.
135</p>
136
137<p class=note>
138Note: calling <a href=socket.html#select><tt>socket.select</tt></a>
139with a server object in
140the <tt>recvt</tt> parameter before a call to <tt>accept</tt> does
141<em>not</em> guarantee <tt>accept</tt> will return immediately. Use the <a
142href=#settimeout><tt>settimeout</tt></a> method or <tt>accept</tt>
143might block until <em>another</em> client shows up.
144</p>
145
146<!-- bind +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
147
148<p class=name id="bind">
149master:<b>bind(</b>address, port<b>)</b>
150</p>
151
152<p class=description>
153Binds a master object to <tt>address</tt> and <tt>port</tt> on the
154local host.
155
156<p class=parameters>
157<tt>Address</tt> can be an IP address or a host name.
158<tt>Port</tt> must be an integer number in the range [0..64K).
159If <tt>address</tt>
160is '<tt>*</tt>', the system binds to all local interfaces
161using the <tt>INADDR_ANY</tt> constant or
162<tt>IN6ADDR_ANY_INIT</tt>, according to the family.
163If <tt>port</tt> is 0, the system automatically
164chooses an ephemeral port.
165</p>
166
167<p class=return>
168In case of success, the method returns 1. In case of error, the
169method returns <b><tt>nil</tt></b> followed by an error message.
170</p>
171
172<p class=note>
173Note: The function <a href=socket.html#bind><tt>socket.bind</tt></a>
174is available and is a shortcut for the creation of server sockets.
175</p>
176
177<!-- close ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
178
179<p class=name id="close">
180master:<b>close()</b><br>
181client:<b>close()</b><br>
182server:<b>close()</b>
183</p>
184
185<p class=description>
186Closes a TCP object. The internal socket used by the object is closed
187and the local address to which the object was
188bound is made available to other applications. No further operations
189(except for further calls to the <tt>close</tt> method) are allowed on
190a closed socket.
191</p>
192
193<p class=note>
194Note: It is important to close all used sockets once they are not
195needed, since, in many systems, each socket uses a file descriptor,
196which are limited system resources. Garbage-collected objects are
197automatically closed before destruction, though.
198</p>
199
200<!-- connect ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
201
202<p class=name id="connect">
203master:<b>connect(</b>address, port<b>)</b>
204</p>
205
206<p class=description>
207Attempts to connect a master object to a remote host, transforming it into a
208client object.
209Client objects support methods
210<a href=#send><tt>send</tt></a>,
211<a href=#receive><tt>receive</tt></a>,
212<a href=#getsockname><tt>getsockname</tt></a>,
213<a href=#getpeername><tt>getpeername</tt></a>,
214<a href=#settimeout><tt>settimeout</tt></a>,
215and <a href=#close><tt>close</tt></a>.
216</p>
217
218<p class=parameters>
219<tt>Address</tt> can be an IP address or a host name.
220<tt>Port</tt> must be an integer number in the range [1..64K).
221</p>
222
223<p class=return>
224In case of error, the method returns <b><tt>nil</tt></b> followed by a string
225describing the error. In case of success, the method returns 1.
226</p>
227
228<p class=note>
229Note: The function <a href=socket.html#connect><tt>socket.connect</tt></a>
230is available and is a shortcut for the creation of client sockets.
231</p>
232
233<p class=note>
234Note: Starting with LuaSocket 2.0,
235the <a href=#settimeout><tt>settimeout</tt></a>
236method affects the behavior of <tt>connect</tt>, causing it to return
237with an error in case of a timeout. If that happens, you can still call <a
238href=socket.html#select><tt>socket.select</tt></a> with the socket in the
239<tt>sendt</tt> table. The socket will be writable when the connection is
240established.
241</p>
242
243<p class=note>
244Note: Starting with LuaSocket 3.0, the host name resolution
245depends on whether the socket was created by <a
246href=#socket.tcp><tt>socket.tcp</tt></a> or <a
247href=#socket.tcp6><tt>socket.tcp6</tt></a>. Addresses from
248the appropriate family are tried in succession until the
249first success or until the last failure.
250</p>
251
252<!-- getpeername ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
253
254<p class=name id="getpeername">
255client:<b>getpeername()</b>
256</p>
257
258<p class=description>
259Returns information about the remote side of a connected client object.
260</p>
261
262<p class=return>
263Returns a string with the IP address of the peer, the
264port number that peer is using for the connection,
265and a string with the family ("<tt>inet</tt>" or "<tt>inet6</tt>").
266In case of error, the method returns <b><tt>nil</tt></b>.
267</p>
268
269<p class=note>
270Note: It makes no sense to call this method on server objects.
271</p>
272
273<!-- getsockname ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
274
275<p class=name id="getsockname">
276master:<b>getsockname()</b><br>
277client:<b>getsockname()</b><br>
278server:<b>getsockname()</b>
279</p>
280
281<p class=description>
282Returns the local address information associated to the object.
283</p>
284
285<p class=return>
286The method returns a string with local IP address, a number with
287the local port,
288and a string with the family ("<tt>inet</tt>" or "<tt>inet6</tt>").
289In case of error, the method returns <b><tt>nil</tt></b>.
290</p>
291
292<!-- getstats +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
293
294<p class=name id="getstats">
295master:<b>getstats()</b><br>
296client:<b>getstats()</b><br>
297server:<b>getstats()</b><br>
298</p>
299
300<p class=description>
301Returns accounting information on the socket, useful for throttling
302of bandwidth.
303</p>
304
305<p class=return>
306The method returns the number of bytes received, the number of bytes sent,
307and the age of the socket object in seconds.
308</p>
309
310<!-- listen ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
311
312<p class=name id="listen">
313master:<b>listen(</b>backlog<b>)</b>
314</p>
315
316<p class=description>
317Specifies the socket is willing to receive connections, transforming the
318object into a server object. Server objects support the
319<a href=#accept><tt>accept</tt></a>,
320<a href=#getsockname><tt>getsockname</tt></a>,
321<a href=#setoption><tt>setoption</tt></a>,
322<a href=#settimeout><tt>settimeout</tt></a>,
323and <a href=#close><tt>close</tt></a> methods.
324</p>
325
326<p class=parameters>
327The parameter <tt>backlog</tt> specifies the number of client
328connections that can
329be queued waiting for service. If the queue is full and another client
330attempts connection, the connection is refused.
331</p>
332
333<p class=return>
334In case of success, the method returns 1. In case of error, the
335method returns <b><tt>nil</tt></b> followed by an error message.
336</p>
337
338<!-- receive ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
339
340<p class=name id="receive">
341client:<b>receive(</b>[pattern [, prefix]]<b>)</b>
342</p>
343
344<p class=description>
345Reads data from a client object, according to the specified <em>read
346pattern</em>. Patterns follow the Lua file I/O format, and the difference in performance between all patterns is negligible.
347</p>
348
349<p class=parameters>
350<tt>Pattern</tt> can be any of the following:
351</p>
352
353<ul>
354<li> '<tt>*a</tt>': reads from the socket until the connection is
355closed. No end-of-line translation is performed;
356<li> '<tt>*l</tt>': reads a line of text from the socket. The line is
357terminated by a LF character (ASCII&nbsp;10), optionally preceded by a
358CR character (ASCII&nbsp;13). The CR and LF characters are not included in
359the returned line. In fact, <em>all</em> CR characters are
360ignored by the pattern. This is the default pattern;
361<li> <tt>number</tt>: causes the method to read a specified <tt>number</tt>
362of bytes from the socket.
363</ul>
364
365<p class=parameters>
366<tt>Prefix</tt> is an optional string to be concatenated to the beginning
367of any received data before return.
368</p>
369
370<p class=return>
371If successful, the method returns the received pattern. In case of error,
372the method returns <tt><b>nil</b></tt> followed by an error
373message, followed by a (possibly empty) string containing
374the partial that was received. The error message can be
375the string '<tt>closed</tt>' in case the connection was
376closed before the transmission was completed or the string
377'<tt>timeout</tt>' in case there was a timeout during the operation.
378</p>
379
380<p class=note>
381<b>Important note</b>: This function was changed <em>severely</em>. It used
382to support multiple patterns (but I have never seen this feature used) and
383now it doesn't anymore. Partial results used to be returned in the same
384way as successful results. This last feature violated the idea that all
385functions should return <tt><b>nil</b></tt> on error. Thus it was changed
386too.
387</p>
388
389<!-- send +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
390
391<p class=name id="send">
392client:<b>send(</b>data [, i [, j]]<b>)</b>
393</p>
394
395<p class=description>
396Sends <tt>data</tt> through client object.
397</p>
398
399<p class=parameters>
400<tt>Data</tt> is the string to be sent. The optional arguments
401<tt>i</tt> and <tt>j</tt> work exactly like the standard
402<tt>string.sub</tt> Lua function to allow the selection of a
403substring to be sent.
404</p>
405
406<p class=return>
407If successful, the method returns the index of the last byte
408within <tt>[i, j]</tt> that has been sent. Notice that, if
409<tt>i</tt> is 1 or absent, this is effectively the total
410number of bytes sent. In case of error, the method returns
411<b><tt>nil</tt></b>, followed by an error message, followed
412by the index of the last byte within <tt>[i, j]</tt> that
413has been sent. You might want to try again from the byte
414following that. The error message can be '<tt>closed</tt>'
415in case the connection was closed before the transmission
416was completed or the string '<tt>timeout</tt>' in case
417there was a timeout during the operation.
418</p>
419
420<p class=note>
421Note: Output is <em>not</em> buffered. For small strings,
422it is always better to concatenate them in Lua
423(with the '<tt>..</tt>' operator) and send the result in one call
424instead of calling the method several times.
425</p>
426
427<!-- setoption ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
428
429<p class=name id="setoption">
430client:<b>setoption(</b>option [, value]<b>)</b><br>
431server:<b>setoption(</b>option [, value]<b>)</b>
432</p>
433
434<p class=description>
435Sets options for the TCP object. Options are only needed by low-level or
436time-critical applications. You should only modify an option if you
437are sure you need it.
438</p>
439
440<p class=parameters>
441<tt>Option</tt> is a string with the option name, and <tt>value</tt>
442depends on the option being set:
443
444<ul>
445
446<li> '<tt>keepalive</tt>': Setting this option to <tt>true</tt> enables
447the periodic transmission of messages on a connected socket. Should the
448connected party fail to respond to these messages, the connection is
449considered broken and processes using the socket are notified;
450
451<li> '<tt>linger</tt>': Controls the action taken when unsent data are
452queued on a socket and a close is performed. The value is a table with a
453boolean entry '<tt>on</tt>' and a numeric entry for the time interval
454'<tt>timeout</tt>' in seconds. If the '<tt>on</tt>' field is set to
455<tt>true</tt>, the system will block the process on the close attempt until
456it is able to transmit the data or until '<tt>timeout</tt>' has passed. If
457'<tt>on</tt>' is <tt>false</tt> and a close is issued, the system will
458process the close in a manner that allows the process to continue as
459quickly as possible. I do not advise you to set this to anything other than
460zero;
461
462<li> '<tt>reuseaddr</tt>': Setting this option indicates that the rules
463used in validating addresses supplied in a call to
464<a href=#bind><tt>bind</tt></a> should allow reuse of local addresses;
465
466<li> '<tt>tcp-nodelay</tt>': Setting this option to <tt>true</tt>
467disables the Nagle's algorithm for the connection;
468
469<li> '<tt>ipv6-v6only</tt>':
470Setting this option to <tt>true</tt> restricts an <tt>inet6</tt> socket to
471sending and receiving only IPv6 packets.
472</ul>
473
474<p class=return>
475The method returns 1 in case of success, or <b><tt>nil</tt></b>
476followed by an error message otherwise.
477</p>
478
479<p class=note>
480Note: The descriptions above come from the man pages.
481</p>
482
483<!-- getoption ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
484
485<p class=name id="getoption">
486client:<b>getoption(</b>option)</b><br>
487server:<b>getoption(</b>option)</b>
488</p>
489
490<p class=description>
491Gets options for the TCP object.
492See <a href=#setoption><tt>setoption</tt></a> for description of the
493option names and values.
494</p>
495
496<p class=parameters>
497<tt>Option</tt> is a string with the option name.
498<ul>
499
500<li> '<tt>keepalive</tt>'
501<li> '<tt>linger</tt>'
502<li> '<tt>reuseaddr</tt>'
503<li> '<tt>tcp-nodelay</tt>'
504</ul>
505
506<p class=return>
507The method returns the option <tt>value</tt> in case of success, or
508<b><tt>nil</tt></b> followed by an error message otherwise.
509</p>
510
511<!-- setstats +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
512
513<p class=name id="setstats">
514master:<b>setstats(</b>received, sent, age<b>)</b><br>
515client:<b>setstats(</b>received, sent, age<b>)</b><br>
516server:<b>setstats(</b>received, sent, age<b>)</b><br>
517</p>
518
519<p class=description>
520Resets accounting information on the socket, useful for throttling
521of bandwidth.
522</p>
523
524<p class=parameters>
525<tt>Received</tt> is a number with the new number of bytes received.
526<tt>Sent</tt> is a number with the new number of bytes sent.
527<tt>Age</tt> is the new age in seconds.
528</p>
529
530<p class=return>
531The method returns 1 in case of success and <tt><b>nil</b></tt> otherwise.
532</p>
533
534<!-- settimeout +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
535
536<p class=name id="settimeout">
537master:<b>settimeout(</b>value [, mode]<b>)</b><br>
538client:<b>settimeout(</b>value [, mode]<b>)</b><br>
539server:<b>settimeout(</b>value [, mode]<b>)</b>
540</p>
541
542<p class=description>
543Changes the timeout values for the object. By default,
544all I/O operations are blocking. That is, any call to the methods
545<a href=#send><tt>send</tt></a>,
546<a href=#receive><tt>receive</tt></a>, and
547<a href=#accept><tt>accept</tt></a>
548will block indefinitely, until the operation completes. The
549<tt>settimeout</tt> method defines a limit on the amount of time the
550I/O methods can block. When a timeout is set and the specified amount of
551time has elapsed, the affected methods give up and fail with an error code.
552</p>
553
554<p class=parameters>
555The amount of time to wait is specified as the
556<tt>value</tt> parameter, in seconds. There are two timeout modes and
557both can be used together for fine tuning:
558</p>
559
560<ul>
561<li> '<tt>b</tt>': <em>block</em> timeout. Specifies the upper limit on
562the amount of time LuaSocket can be blocked by the operating system
563while waiting for completion of any single I/O operation. This is the
564default mode;</li>
565
566<li> '<tt>t</tt>': <em>total</em> timeout. Specifies the upper limit on
567the amount of time LuaSocket can block a Lua script before returning from
568a call.</li>
569</ul>
570
571<p class=parameters>
572The <b><tt>nil</tt></b> timeout <tt>value</tt> allows operations to block
573indefinitely. Negative timeout values have the same effect.
574</p>
575
576<p class=note>
577Note: although timeout values have millisecond precision in LuaSocket,
578large blocks can cause I/O functions not to respect timeout values due
579to the time the library takes to transfer blocks to and from the OS
580and to and from the Lua interpreter. Also, function that accept host names
581and perform automatic name resolution might be blocked by the resolver for
582longer than the specified timeout value.
583</p>
584
585<p class=note>
586Note: The old <tt>timeout</tt> method is deprecated. The name has been
587changed for sake of uniformity, since all other method names already
588contained verbs making their imperative nature obvious.
589</p>
590
591<!-- shutdown +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
592
593<p class=name id="shutdown">
594client:<b>shutdown(</b>mode<b>)</b><br>
595</p>
596
597<p class=description>
598Shuts down part of a full-duplex connection.
599</p>
600
601<p class=parameters>
602Mode tells which way of the connection should be shut down and can
603take the value:
604<ul>
605<li>"<tt>both</tt>": disallow further sends and receives on the object.
606This is the default mode;
607<li>"<tt>send</tt>": disallow further sends on the object;
608<li>"<tt>receive</tt>": disallow further receives on the object.
609</ul>
610
611<p class=return>
612This function returns 1.
613</p>
614
615<!-- dirty +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
616
617<p class=name id="dirty">
618master:<b>dirty()</b><br>
619client:<b>dirty()</b><br>
620server:<b>dirty()</b>
621</p>
622
623<p class=description>
624Check the read buffer status.
625</p>
626
627<p class=return>
628Returns <tt>true</tt> if there is any data in the read buffer, <tt>false</tt> otherwise.
629</p>
630
631<p class=note>
632Note: <b>This is an internal method, any use is unlikely to be portable.</b>
633</p>
634
635<!-- getfd +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
636
637<p class=name id="getfd">
638master:<b>getfd()</b><br>
639client:<b>getfd()</b><br>
640server:<b>getfd()</b>
641</p>
642
643<p class=description>
644Returns the underling socket descriptor or handle associated to the object.
645</p>
646
647<p class=return>
648The descriptor or handle. In case the object has been closed, the return will be -1.
649</p>
650
651<p class=note>
652Note: <b>This is an internal method, any use is unlikely to be portable.</b>
653</p>
654
655<!-- setfd +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
656
657<p class=name id="setfd">
658master:<b>setfd(</b>fd<b>)</b><br>
659client:<b>setfd(</b>fd<b>)</b><br>
660server:<b>setfd(</b>fd<b>)</b>
661</p>
662
663<p class=description>
664Sets the underling socket descriptor or handle associated to the object. The current one is simply replaced, not closed, and no other change to the object state is made.
665</p>
666
667<p class=return>
668No return value.
669</p>
670
671<p class=note>
672Note: <b>This is an internal method, any use is unlikely to be portable.</b>
673</p>
674
675<!-- footer +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
676
677<div class=footer>
678<hr>
679<center>
680<p class=bar>
681<a href="index.html">home</a> &middot;
682<a href="index.html#down">download</a> &middot;
683<a href="installation.html">installation</a> &middot;
684<a href="introduction.html">introduction</a> &middot;
685<a href="reference.html">reference</a>
686</p>
687<p>
688<small>
689Last modified by Diego Nehab on <br>
690Thu Apr 20 00:25:57 EDT 2006
691</small>
692</p>
693</center>
694</div>
695
696</body>
697</html>
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-04-04 22:35:35 +0000