Hand-drawn whiteboard-style infographic explaining the TCP three-way handshake with a clear left-to-right sequence of Client Host, Network Path, Server Host, and established application flow. This pert cpm network diagram example uses cool blue sketch lines, packet arrows, TCP state notes, and a developer-friendly legend for a clean editorial tech brand look.
Re-render this exact infographic with every label, heading and caption translated. We re-use all the original attributes (topic, style, palette, …) and only swap the language.
Currently in English.
Tech architecture infographic titled "TCP Three-Way Handshake" using archetype PROTOCOL HANDSHAKE for a mid-level developer audience. Show a clean left-to-right sequence between labeled boxes connected by directional arrows: Client Host, Network Path, Server Host, and optional Application Ready state. Each box must contain an icon, a canonical English component name, and a one-line English role description. Example boxes: Client Host — 'Initiates TCP connection'; Network Path — 'Transfers TCP segments between endpoints'; Server Host — 'Listens on a TCP port and replies'; Application Ready — 'Connection established for data exchange'. Use numbered exchanges with technically accurate TCP flow: 1) Client Host sends SYN to Server Host with label 'TCP SYN, Seq=x'; 2) Server Host replies with SYN-ACK with label 'TCP SYN-ACK, Seq=y, Ack=x+1'; 3) Client Host sends ACK with label 'TCP ACK, Ack=y+1'; then show established state with a final arrow or state label 'TCP connection established'. Include small side annotations in English for TCP states where useful: 'SYN-SENT', 'SYN-RECEIVED', 'ESTABLISHED'. Add subtle packet icons near arrows. Because the requested generic boxes were mentioned, include a secondary small reference strip of generic labeled boxes for Browser, API, Cache, Queue, Database as optional downstream consumers, each with icon, English name, and one-line role description, connected after the established TCP connection to show that application traffic may follow; arrow labels should be technically accurate such as 'HTTPS request', 'REST JSON', 'Cache lookup', 'Enqueue job', 'SQL query'. Add a numbered legend 1-7 in English walking through the lifecycle: 1. Client opens a TCP connection to a server port. 2. Client sends SYN with its initial sequence number. 3. Server receives SYN and allocates connection state. 4. Server responds with SYN-ACK acknowledging the client sequence. 5. Client validates SYN-ACK and sends final ACK. 6. Both sides enter ESTABLISHED and can exchange application data. 7. Higher-level protocols such as HTTPS or REST can now use the TCP session. Make the layout visually clear, with labeled boxes, arrowheads showing direction, concise English captions, and no claim that this is an audited or reference-secure architecture. Visual style: hand-drawn whiteboard, cool blue and cyan palette, sketchy marker outlines, light grid or whiteboard texture, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. All text MUST be written in English (array). Every heading, label, caption, legend and metric name in the image must be in English — not English. Spell each English word correctly using English characters and diacritics. Numbers stay as digits, no real cloud-vendor logos (AWS / GCP / Azure) — use generic cloud icons, no watermarks No real cloud-vendor logos (AWS, GCP, Azure) beyond generic cloud icons. Common protocol names (HTTPS, TCP, JWT, OAuth, REST, GraphQL) stay in canonical English form. No security-claim overstatements (do not present diagrams as audited reference architectures).
Report inappropriate content
Tell us why this image is inappropriate. A description is required — generic submissions are dismissed.
Confirmed reports are resolved within 24 hours.
