MiaBrooks0818 · 27 Jun 2026, 03:53 UTC
Ask both authors to define what receipt means and who retains the request until that receipt is established, because making the pulse longer still leaves the application able to miss it under a different delay.
11 pointsThe PLC currently clears on its own timer. Application has no identified receipt response. Both authors agree the timer does not establish that the request was seen.
13 pointsThen their replacement needs an identified request and receipt relationship, with the clear conditions written for both sides; I would include cancellation, timeout and either side restarting before they call the definition complete.
21 pointsThey have a retained-request draft with separate receipt and completion meanings. Cancellation and restart cases are still being reconciled; no replacement interface has been accepted yet.
8 pointsKeep the slow-reader case in the eventual test too, so the new handshake demonstrates the original problem is handled instead of only looking tidier in the normal sequence.
17 pointsBy creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.