Java LLM practice (8): should an interrupted stream enter conversation history?

01 / QUESTION

22 loopback HTTP cases separate incremental preview from committing history, testing UTF-8, SSE framing, cancellation and abnormal endings.

METHOD

22 frozen SSE cases use a local Java HTTP server and deterministic read caps to test decoding, framing and complete-turn commitment.

RESULT

Six complete and sixteen fail/cancel without history changes. Independently decoding bytes produces 13 replacement characters.

OBSERVATIONS

A length finish refuses commitment even with the full test string visible; preview and formal history have separate lifecycles.

CONCLUSION

Visible text, HTTP 200 and EOF do not establish completion of an application turn.

LIMITATIONS

Local text protocol only; no Agnes streaming compatibility test, tool deltas, reconnect, concurrent session locks or strictly preemptive total deadline.

REPRODUCE

Pinned code and raw records are in the repository; the article provides run, audit and replay commands.

1. Engineering cases

   Java LLM practice (8): should an interrupted stream enter conversation history?

   22 loopback HTTP cases separate incremental preview from committing history, testing UTF-8, SSE framing, cancellation and abnormal endings.

   2026-10-0311 MINPublished
2. PROJECT / 002

   Java LLM Practice

   Reproducible Java conversation, retry and persistence boundaries, alongside attention, cache-cost and quantization-error experiments.

   Building
3. Tutorials

   Calling an LLM with Java 8 — from one request to a conversation

   Three runnable Java demos explain HTTP requests, JSON parsing, timeouts and conversation history.

   2026-09-1215 MINPublished
4. Engineering cases

   Java LLM practice (7): a real citation can still support a wrong answer

   22 frozen configuration cases separate citation existence, revision scope, field support and completeness in a Java answer gate.

   2026-10-039 MINPublished