-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
New translations tcpeventclass.md (Spanish)
- Loading branch information
Showing
1 changed file
with
61 additions
and
0 deletions.
There are no files selected for viewing
61 changes: 61 additions & 0 deletions
61
i18n/es/docusaurus-plugin-content-docs/version-20-R8/API/TCPEventClass.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,61 @@ | ||
--- | ||
id: TCPEventClass | ||
title: TCPEvent | ||
--- | ||
|
||
The `TCPEvent` class provides information about events occurring during the lifecycle of a TCP connection. It is generated when a [TCPConnection](TCPConnectionClass.md) is opened and is typically utilized in callbacks such as `onConnection`, `onData`, `onError`, and others. | ||
|
||
<details><summary>Historia</summary> | ||
|
||
| Lanzamiento | Modificaciones | | ||
| ----------- | -------------- | | ||
| 20 R8 | Clase añadida | | ||
|
||
</details> | ||
|
||
### TCPEvent Object | ||
|
||
A `TCPEvent` object is immutable and non-streamable. | ||
|
||
Las siguientes propiedades están disponibles: | ||
|
||
| | | ||
| --------------------------------------------------------------------------------------------------- | | ||
| [<!-- INCLUDE ##4D.TCPEvent.type.Syntax -->](#type)<br/><!-- INCLUDE ##4D.TCPEvent.type.Summary --> | | ||
| [<!-- INCLUDE #4D.TCPEvent.data.Syntax -->](#data)<br/><!-- INCLUDE #4D.TCPEvent.data.Summary --> | | ||
|
||
<!-- REF #4D.TCPEvent.type.Desc --> | ||
|
||
## .type | ||
|
||
<!-- REF #4D.TCPEvent.type.Syntax -->**type** : Text<!-- END REF --> | ||
|
||
#### Descripción | ||
|
||
The `.type` property contains <!-- REF #4D.TCPEvent.type.Summary -->the type of the event<!-- END REF -->. Los valores posibles son: | ||
|
||
- `"connection"`: Indicates that a TCPConnection was successfully established. | ||
- `"data"`: Indicates that data has been received. | ||
- `"error"`: Indicates that an error occurred during the TCPConnection. | ||
- `"close"`: Indicates that the TCPConnection has been properly closed. | ||
- `"terminate"`: Indicates that the TCPConnection is about to be released. | ||
|
||
<!-- END REF --> | ||
|
||
<!-- REF #4D.TCPEvent.data.Desc --> | ||
|
||
## .data | ||
|
||
<!-- REF #4D.TCPEvent.data.Syntax -->**data** : Blob<!-- END REF --> | ||
|
||
#### Descripción | ||
|
||
The `.data` property contains <!-- REF #4D.TCPEvent.data.Summary -->the data associated with the event<!-- END REF -->. It is only valid for events of type `"data"`. | ||
|
||
:::note | ||
|
||
When working with low-level TCP/IP connections, keep in mind there is no guarantee that all data will arrive in a single packet. Data arrives in order but may be fragmented across multiple packets. | ||
|
||
::: | ||
|
||
<!-- END REF --> |