---
title: "Comment by Ahmet Özel on \"Why AI replies stream word-by-word\" | Hashnode"
description: "The separation between generation latency and perceived latency is useful, and the moderation-buffering example shows that delaying delivery can have a real pur"
url: "https://hashnode.com/posts/why-ai-replies-stream-word-by-word/6ac34ccf409651402523c315/comment/6ac39a2f6dbf382c5678bc73"
---

[Discussion](https://hashnode.com/posts/why-ai-replies-stream-word-by-word/6ac34ccf409651402523c315)

Comment [Why AI replies stream word-by-word](https://hashnode.com/posts/why-ai-replies-stream-word-by-word/6ac34ccf409651402523c315)

[Ahmet Özel](https://hashnode.com/@ahmetozel)

[Oct 5](https://hashnode.com/posts/why-ai-replies-stream-word-by-word/6ac34ccf409651402523c315/comment/6ac39a2f6dbf382c5678bc73)

The separation between generation latency and perceived latency is useful, and the moderation-buffering example shows that delaying delivery can have a real purpose. I would distinguish transport packet loss from a broken application stream in the failure section: HTTP over TCP already recovers ordinary packet loss while the connection survives.

The harder UI case is a reconnect after the response was partly displayed. A test could cut the connection after a complete SSE event, then check whether the client marks the answer incomplete, restarts it or resumes from an application event ID. That makes the reliability tradeoff explicit without treating every dropped packet as permanently lost generated text.

[Nagappan S](https://hashnode.com/@imkarthik03)

[Oct 13](https://hashnode.com/posts/why-ai-replies-stream-word-by-word/6ac34ccf409651402523c315/comment/6ac39a2f6dbf382c5678bc73#reply-6acdd2d3e5d5c9e441728b07)

Fair correction. TCP already recovers ordinary packet loss, so the real failure is the connection dropping mid-response. The reconnect test you describe is the right one: cut after a complete SSE event, then check whether the client marks the answer incomplete, restarts, or resumes from an event ID. I'd make resume-by-event-ID the target, since it avoids both a visible glitch and regenerating the whole answer.

[Ahmet Özel](https://hashnode.com/@ahmetozel)

[Oct 15](https://hashnode.com/posts/why-ai-replies-stream-word-by-word/6ac34ccf409651402523c315/comment/6ac39a2f6dbf382c5678bc73#reply-6ad13cf41ea769204fa560e8)

Resume-by-event-ID works when the server can replay the same generation, including events produced while the client was disconnected. An event ID alone cannot resume text that was never retained, and starting a fresh generation can diverge from the prefix already displayed.

I would make replay retention and expiry explicit. The reconnect test can first replay a saved suffix without duplicating the last displayed event, then repeat after retention expires and require an incomplete-or-restart outcome rather than silently splicing two different answers together.
