These might be signs that the
LineReaderwould be better off as its own process i.e. Task/Agent/Genserver so it can keep track of its own state. I’d be curious what else it’s being used for and how else it’s being used.
Yes, I thought about such approach, but feels very heavy-weight. As I understand it you have to link that additional process into the supervision hierarchy, figure out how to pass it’s pid to the “main” process, transition the resources to the additional process (the socket port in this case) - that’s like two pages of code, too much.
or rolled into
ClientHandler
It’s used in several places, not only in the ClientHandler, so I wanted to avoid code duplication. In this case it’s not much, maybe 10 lines, but these lines better be carefuly tested.
