netty5/handler
Chris Vest b3d3269b8c
Avoid overspecifying ScheduledFuture when Future will do (#11636)
Motivation:
Overspecifying interfaces can increase coupling and make refactoring harder down the line.

Modification:
Places that were specifying fields, variables, and return types as ScheduledFuture, but did not use any features specific to ScheduledFuture, have been changed to specify Future instead.

Result:
Cleaner code.
2021-08-31 16:05:21 +02:00
..
src Avoid overspecifying ScheduledFuture when Future will do (#11636) 2021-08-31 16:05:21 +02:00
pom.xml [maven-release-plugin] prepare for next development iteration 2021-08-16 08:23:23 +00:00