Skip to content
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

toService API #61

Open
wants to merge 10 commits into
base: master
Choose a base branch
from
Open

toService API #61

wants to merge 10 commits into from

Conversation

jeremyrsmith
Copy link
Collaborator

@jeremyrsmith jeremyrsmith commented May 9, 2017

This commit makes the following changes:

  • Enable a new preferred API, toService. This API allows for creating a service from a request. Rather than specifying content up-front, you can create a function Content => Future[Result] using the toService API, which gives a reusable function from a request specification.
  • Major refactoring of types. All request types have been unified to a single HTTPRequest type, which is not path-dependent. A ClientRequest type also wraps this with a provided client.
  • Functionality is implemented mainly through Filters now, which composes better with the rest of the finagle ecosystem.

Jeremy Smith and others added 9 commits January 23, 2018 10:10
- Add the ability to place filters before the HTTP service, configurable
  at the request level
- Add the concept of an Authorizer, which is just a filter.
- Add some initial Authorizers - Bearer (for pre-shared Bearer tokens)
  and MAC (for pre-shared MAC tokens)

A future PR should contain a full OAuth2 flow implemented in an
Authorizer.
This commit makes the following changes:

* Enable a new preferred API, `toService`. This API allows for creating
  a service from a request. Rather than specifying content up-front, you
  can create a function `Content => Future[Result]` using the `toService`
  API, which gives a reusable function from a request specification.
* Major refactoring of types. All request types have been unified to a
  single `HTTPRequest` type, which is not path-dependent. A
  `ClientRequest` type also wraps this with a provided client.
* Use strings for method singleton types (workaround breaking finagle change)
* Move code around & remove json dependency from core tests
* Update build.sbt based on master
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.

1 participant