344
Platforms
©2000-2008 Tibbo Technology Inc.
Declaration:
on_sock_overrun
See Also:
---
Details
Normally, overruns can only happen for UDP communications as UDP has no "data
flow control" and, hence, data overruns are normal. Another on_sock_overrun
event on a particular socket is never generated until the previous one is processed.
When the event handler for this event is entered the
is automatically
switched to the socket on which this event was generated.
On_sock_postdata
Function:
Generated when at least one data byte is present in the
VAR buffer of the socket, but only after the VAR buffer
has become full at least once in the cause of the current
HTTP request processing.
Declaration:
on_sock_postdata
See Also:
Details
HTTP requests can contain large amount of HTTP variable data, which is stored into
the VAR buffer. The amount of such data can exceed the VAR buffer capacity. If
this is not handled properly, the HTTP request execution may stall indefinitely --
see
.
After the socket accepts an HTTP connection, this event is not generated (for this
particular connection) until the VAR buffer becomes full. Once this happened, the
event is generated even if there is a single byte waiting to be processed in the
buffer. Two same-socket on_sock_postdata events never wait in the queue -- the
next event can only be generated after the previous one is processed.
When the event handler for this event is entered the
property is
automatically switched to the socket for which this event was generated.
method or
property to work
with the VAR buffer's data.
On_sock_tcp_packet_arrival Event
Function:
Notifies your program that the TCP packet of a certain
size has arrived.
Syntax:
on_sock_tcp_packet_arrival(len as word)
See Also:
"Split Packet" Mode of TCP Data Processing
Part
Description
340
365
323
340
333
336
306