Skip to content

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

Merged
merged 5 commits into from
Nov 11, 2016

Conversation

NiteshKant
Copy link
Contributor

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.

#### 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.
@NiteshKant
Copy link
Contributor Author

\cc @stevegury

Copy link
Member

@stevegury stevegury left a 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.

@NiteshKant
Copy link
Contributor Author

AvailabilitySupplier?

@NiteshKant
Copy link
Contributor Author

@stevegury should we merge for now (I need to move fwd with changes related to events) and revisit the name later?

@NiteshKant NiteshKant changed the title Extract interface AvailabilityProvider Extract interface Availability Nov 11, 2016
@NiteshKant
Copy link
Contributor Author

@stevegury I renamed AvailabilityProvider to Availability

@stevegury
Copy link
Member

(For lack of a better word)

@stevegury stevegury merged commit f87d508 into rsocket:0.5.x Nov 11, 2016
@NiteshKant NiteshKant deleted the 0.5.x-avail-provider branch November 11, 2016 23:07
NiteshKant added a commit that referenced this pull request Dec 8, 2016
* 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`
NiteshKant added a commit to NiteshKant/reactivesocket-java that referenced this pull request Dec 14, 2016
* 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`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants