Follow-up from "TCP accept refactoring" - clean up naming of isc__netievent etc.
The following discussion from !3320 (merged) should be addressed:
-
@each started a discussion: It isn't urgent, or even new in this branch, but I just noticed for the first time that in some of these names you have a double underscore after
netievent
as well as before, and I'm wondering what that signifies?