Source strings

198 Strings 100%
Browse Translate
8,721 Words 100%
This translation is being used as source strings within this component.

Strings status

198
All strings — 8,721 words Browse Translate Zen
198
Read-only strings — 8,721 words Browse Translate Zen
7
Strings with any failing checks — 226 words Browse Translate Zen
7
Failing check: Ellipsis — 226 words Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
exercises/ex-sharing This language is used for source strings. This component is linked to the cnp3-ebook/index repository. CC-BY-SA-3.0 0 0 0 0 0 0 0
exercises/intro This language is used for source strings. This component is linked to the cnp3-ebook/index repository. CC-BY-SA-3.0 0 0 0 0 0 0 0
exercises/reliability This language is used for source strings. This component is linked to the cnp3-ebook/index repository. CC-BY-SA-3.0 0 0 0 0 0 0 0
exercises/transport This language is used for source strings. This component is linked to the cnp3-ebook/index repository. CC-BY-SA-3.0 0 0 0 0 0 0 0
principles/naming This language is used for source strings. This component is linked to the cnp3-ebook/index repository. CC-BY-SA-3.0 0 0 0 0 1 0 0
principles/referencemodels This language is used for source strings. This component is linked to the cnp3-ebook/index repository. CC-BY-SA-3.0 0 0 0 0 0 0 0
principles/security This language is used for source strings. This component is linked to the cnp3-ebook/index repository. CC-BY-SA-3.0 0 0 0 0 1 0 0
exercises/dns This language is used for source strings. This component is linked to the cnp3-ebook/index repository. CC-BY-SA-3.0 0 0 0 0 3 0 0
exercises/http This language is used for source strings. This component is linked to the cnp3-ebook/index repository. CC-BY-SA-3.0 0 0 0 0 0 0 0
exercises/lan This language is used for source strings. This component is linked to the cnp3-ebook/index repository. CC-BY-SA-3.0 0 0 0 0 0 0 0
Browse all components

Overview

Project website www.computer-networking.info
Project maintainers User avatar obonaventure User avatar qdeconinck
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Translation license Creative Commons Attribution Share Alike 3.0 Unported
Source code repository https://github.com/cnp3/ebook
Repository branch master
Last remote commit Merge pull request #126 from INGIbot/weblate-cnp3-ebook-index d9f8d8f
Olivier Bonaventure authored 7 months ago
Weblate repository https://weblate.info.ucl.ac.be/git/cnp3-ebook/index/
File mask locale/*/LC_MESSAGES/protocols/tcp.po
Translation file Download locale/pot/protocols/tcp.pot
Last change None
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 198 8,721 53,856
Translated 100% 198 100% 8,721 100% 53,856
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 198 100% 8,721 100% 53,856
Failing checks 3% 7 2% 226 3% 1,621
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

8,721
Hosted words
198
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
—
—
Hosted strings
—
—
Translated
—
—
Contributors
—
User avatar None

Resource update

cnp3-ebook / protocols/tcp — English

File locale/pot/protocols/tcp.pot was added. 2 years ago
User avatar None

String updated in the repository

cnp3-ebook / protocols/tcp — English

The :math:`2*MSL` seconds delay in the `TIME\_WAIT` state is an important operational problem on servers having thousands of simultaneously opened TCP connections [FTY99]_. Consider for example a busy web server that processes 10.000 TCP connections every second. If each of these connections remains in the `TIME\_WAIT` state for 4 minutes, this implies that the server would have to maintain more than 2 million TCBs at any time. For this reason, some TCP implementations prefer to perform an abrupt connection release by sending a `RST` segment to close the connection [AW05]_ and immediately discard the corresponding :term:`TCB`. However, if the `RST` segment is lost, the remote host continues to maintain a :term:`TCB` for a connection that no longer exists. This optimization reduces the number of TCBs maintained by the host sending the `RST` segment but at the potential cost of increased processing on the remote host when the `RST` segment is lost.
The :math:`2*MSL` seconds delay in the `TIME\_WAIT` state is an important operational problem on servers having thousands of simultaneously opened TCP connections [FTY99]_. Consider for example a busy web server that processes 10.000 TCP connections every second. If each of these connections remains in the `TIME\_WAIT` state for 4 minutes, this implies that the server would have to maintain more than 2 million TCBs at any time. For this reason, some TCP implementations prefer to perform an abrupt connection release by sending a `RST` segment to close the connection [AW05]_ and immediately discard the corresponding :term:`TCB`. However, if the `RST` segment is lost, the remote host continues to maintain a :term:`TCB` for a connection that no longer exists. This optimization reduces the number of TCBs maintained by the host sending the `RST` segment but at the potential cost of increased processing on the remote host when the `RST` segment is lost.
2 years ago
User avatar None

String updated in the repository

cnp3-ebook / protocols/tcp — English

The second path is when the host has transmitted all data. Assume that the last transmitted sequence number is `z`. Then, the host sends a `FIN` segment with sequence number :math:`(z+1) \pmod{2^{32}}` and enters the `FIN_WAIT1` state. In this state, it can retransmit unacknowledged segments but cannot send new data segments. It waits for an acknowledgment of its `FIN` segment (i.e. sequence number :math:`(z+1) \pmod{2^{32}}`), but may receive a `FIN` segment sent by the remote host. In the first case, the TCP connection enters the `FIN\_WAIT2` state. In this state, new data segments from the remote host are still accepted until the reception of the `FIN` segment. The acknowledgment for this `FIN` segment is sent once all data received before the `FIN` segment have been delivered to the user and the connection enters the `TIME\_WAIT` state. In the second case, a `FIN` segment is received and the connection enters the `Closing` state once all data received from the remote host have been delivered to the user. In this state, no new data segments can be sent and the host waits for an acknowledgment of its `FIN` segment before entering the `TIME\_WAIT` state.
The second path is when the host has transmitted all data. Assume that the last transmitted sequence number is `z`. Then, the host sends a `FIN` segment with sequence number :math:`(z+1) \pmod{2^{32}}` and enters the `FIN_WAIT1` state. In this state, it can retransmit unacknowledged segments but cannot send new data segments. It waits for an acknowledgment of its `FIN` segment (i.e. sequence number :math:`(z+1) \pmod{2^{32}}`), but may receive a `FIN` segment sent by the remote host. In the first case, the TCP connection enters the `FIN\_WAIT2` state. In this state, new data segments from the remote host are still accepted until the reception of the `FIN` segment. The acknowledgment for this `FIN` segment is sent once all data received before the `FIN` segment have been delivered to the user and the connection enters the `TIME\_WAIT` state. In the second case, a `FIN` segment is received and the connection enters the `Closing` state once all data received from the remote host have been delivered to the user. In this state, no new data segments can be sent and the host waits for an acknowledgment of its `FIN` segment before entering the `TIME\_WAIT` state.
2 years ago
Browse all translation changes