-
Notifications
You must be signed in to change notification settings - Fork 356
Extract interface Availability
#191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
#### Problem `DuplexConnection`, `ReactiveSocket` and `ReactiveSocketClient` all provide a method `double availability()` and so can benefit from having a common interface. This will be useful for giving event callbacks that retrieve availability as availability follows a pull model instead of push. #### Modification Added a new interface `AvailabilityProvider` and have the other interfaces extend it. #### Result Common way to access availabilty.
\cc @stevegury |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the idea but dislike the long name AvailabilityProvider
.
I would prefer something shorter, I don't have a good idea maybe just Available
.
|
@stevegury should we merge for now (I need to move fwd with changes related to events) and revisit the name later? |
AvailabilityProvider
Availability
@stevegury I renamed |
(For lack of a better word) |
* Extract interface `AvailabilityProvider` #### Problem `DuplexConnection`, `ReactiveSocket` and `ReactiveSocketClient` all provide a method `double availability()` and so can benefit from having a common interface. This will be useful for giving event callbacks that retrieve availability as availability follows a pull model instead of push. #### Modification Added a new interface `AvailabilityProvider` and have the other interfaces extend it. #### Result Common way to access availabilty. * Rename `AvailabilityProvider` to `Availability`
* Extract interface `AvailabilityProvider` `DuplexConnection`, `ReactiveSocket` and `ReactiveSocketClient` all provide a method `double availability()` and so can benefit from having a common interface. This will be useful for giving event callbacks that retrieve availability as availability follows a pull model instead of push. Added a new interface `AvailabilityProvider` and have the other interfaces extend it. Common way to access availabilty. * Rename `AvailabilityProvider` to `Availability`
Problem
DuplexConnection
,ReactiveSocket
andReactiveSocketClient
all provide a methoddouble availability()
and so can benefit from having a common interface.This will be useful for giving event callbacks that retrieve availability as availability follows a pull model instead of push.
Modification
Added a new interface
AvailabilityProvider
and have the other interfaces extend it.Result
Common way to access availabilty.