[Server] Simplify server entrypoint with run-based transport lifecycle #103
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR replaces the old
connect()+listen()flow with a singlerun()method that wires, executes, and tears down transports for every example, doc, and transport implementation.Motivation and Context
connect()andlisten()and worry about cleanup.initialize,onMessage,listen,close) while the server coordinates their use and always closes them oncelisten()finishes...whether that’s a blocking STDIO loop, a one-shot HTTP request, or blocking asynchronous loop.What’s Changed
Server::run()which initializes the transport, hooks up callbacks, runslisten(), closes the transport, and returns whatever the transport returns.0for success,1whenSTDINreading fails) and cleared session state during close.run()and, for STDIO scripts, exit with the returned status.run()instead of invokinglisten()manually.Breaking Changes
Server::connect()has been removed. All consumers must callServer::run($transport)and drop their manual$transport->listen()/$transport->close()calls (if any).