On Wednesday, 3 May 2017 at 07:35:56 UTC, Stefan Koch wrote:
On Wednesday, 3 May 2017 at 06:10:22 UTC, Adrian Matoga wrote:
So you're going to reinvent TCP in your debugging protocol?
No. there is no need for a full blown recovery mechanism.
For the typical usecase a lossless orderd connection can be
assumed.
And most things are not order dependent
The debugger isn't a massive, real-time system that needs to
service thousands of clients and squeeze as much performance out
of the network as possible. The overhead incurred by TCP is
essentially not worth considering for something that's going to
be run over localhost 90%, and service just the one client.
Reinventing the wheel adds a far bigger overhead: Maintaining
your new protocol.
TCP implementations are readily available. They're well
maintained, well documented, and are essentially guaranteed to
work across platforms.
Implementing a new protocol just adds an extra point of breakage
for little to no gain. It also incurs the cost of the associated
development time, and - down the line - any time spent fixing or
iterating. Not to mention that tests need to be written,
documentation needs to be put in place.
A classic case of premature optimization.
