Delay Building Of a Request
up vote
2
down vote
favorite
I'm trying to create a third party library to consume an API.
I've created a bunch of classes which resolve different api calls e.g:
public class AccountsEndpoint: IAccountsEndpoint
{
public async Task<Account> GetAsync(id)
{
return await this.BuildUrl(id).GetJsonAsync();
}
//etc...
}
public class NotificationsEndpoint: INotificationsEndpoint
{
public async Task<Notification> SetPrimary(id)
{
return await this.BuildUrl(id).AppendSegment("Primary")
.PostJsonAsync(null, cancellationToken)
.ReceiveJson<Notification>())();
}
}
I have a large number of these endpoints and I would like to run some additional code before each one of these calls,
e.g For example if my oauth token is invalid I would want to get a new access token and retry the request automatically.
I would prefer NOT to have to wrap all api calls with a handler like:
public async Task<Notification> SetPrimary(id)
{
return await new CustomErrorHandler(() =>
this.BuildUrl(id).AppendSegment("Primary")
.PostJsonAsync(null, cancellationToken)
.ReceiveJson<Notification>())()).ExecuteAsync();
}
If I were to do something like that I would have to remember to use the error handler on all endpoint, when I feel like there's a better way to invert the control. (Alternatively, I could generate dummy interface and have the wrapping logic there but that arises the same issues as manually adding the calls).
How can I wrap all of the calls with error handler logic?
c# .net rest architecture
|
show 4 more comments
up vote
2
down vote
favorite
I'm trying to create a third party library to consume an API.
I've created a bunch of classes which resolve different api calls e.g:
public class AccountsEndpoint: IAccountsEndpoint
{
public async Task<Account> GetAsync(id)
{
return await this.BuildUrl(id).GetJsonAsync();
}
//etc...
}
public class NotificationsEndpoint: INotificationsEndpoint
{
public async Task<Notification> SetPrimary(id)
{
return await this.BuildUrl(id).AppendSegment("Primary")
.PostJsonAsync(null, cancellationToken)
.ReceiveJson<Notification>())();
}
}
I have a large number of these endpoints and I would like to run some additional code before each one of these calls,
e.g For example if my oauth token is invalid I would want to get a new access token and retry the request automatically.
I would prefer NOT to have to wrap all api calls with a handler like:
public async Task<Notification> SetPrimary(id)
{
return await new CustomErrorHandler(() =>
this.BuildUrl(id).AppendSegment("Primary")
.PostJsonAsync(null, cancellationToken)
.ReceiveJson<Notification>())()).ExecuteAsync();
}
If I were to do something like that I would have to remember to use the error handler on all endpoint, when I feel like there's a better way to invert the control. (Alternatively, I could generate dummy interface and have the wrapping logic there but that arises the same issues as manually adding the calls).
How can I wrap all of the calls with error handler logic?
c# .net rest architecture
I am a bit confused by the presented code as it does not provide enough context for me to have a clear picture of what it is suppose to be doing. That said however, you mentioned pipeline and the middleware pattern came to mind. If you have a pipeline that manages requests then you can insert a middleware early in the pipeline that was satisfy the behavior you seek
– Nkosi
Nov 12 at 3:23
similar to how message handlers are used in Web API
– Nkosi
Nov 12 at 3:28
@nkosi thanks for your response I’ll check that out
– johnny 5
Nov 12 at 3:35
You appear to be using Flurl. these might be of some interest to you. flurl.io/docs/configuration and flurl.io/docs/extensibility
– Nkosi
Nov 13 at 1:48
1
not if you apply it globally.
– Nkosi
Nov 13 at 1:56
|
show 4 more comments
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I'm trying to create a third party library to consume an API.
I've created a bunch of classes which resolve different api calls e.g:
public class AccountsEndpoint: IAccountsEndpoint
{
public async Task<Account> GetAsync(id)
{
return await this.BuildUrl(id).GetJsonAsync();
}
//etc...
}
public class NotificationsEndpoint: INotificationsEndpoint
{
public async Task<Notification> SetPrimary(id)
{
return await this.BuildUrl(id).AppendSegment("Primary")
.PostJsonAsync(null, cancellationToken)
.ReceiveJson<Notification>())();
}
}
I have a large number of these endpoints and I would like to run some additional code before each one of these calls,
e.g For example if my oauth token is invalid I would want to get a new access token and retry the request automatically.
I would prefer NOT to have to wrap all api calls with a handler like:
public async Task<Notification> SetPrimary(id)
{
return await new CustomErrorHandler(() =>
this.BuildUrl(id).AppendSegment("Primary")
.PostJsonAsync(null, cancellationToken)
.ReceiveJson<Notification>())()).ExecuteAsync();
}
If I were to do something like that I would have to remember to use the error handler on all endpoint, when I feel like there's a better way to invert the control. (Alternatively, I could generate dummy interface and have the wrapping logic there but that arises the same issues as manually adding the calls).
How can I wrap all of the calls with error handler logic?
c# .net rest architecture
I'm trying to create a third party library to consume an API.
I've created a bunch of classes which resolve different api calls e.g:
public class AccountsEndpoint: IAccountsEndpoint
{
public async Task<Account> GetAsync(id)
{
return await this.BuildUrl(id).GetJsonAsync();
}
//etc...
}
public class NotificationsEndpoint: INotificationsEndpoint
{
public async Task<Notification> SetPrimary(id)
{
return await this.BuildUrl(id).AppendSegment("Primary")
.PostJsonAsync(null, cancellationToken)
.ReceiveJson<Notification>())();
}
}
I have a large number of these endpoints and I would like to run some additional code before each one of these calls,
e.g For example if my oauth token is invalid I would want to get a new access token and retry the request automatically.
I would prefer NOT to have to wrap all api calls with a handler like:
public async Task<Notification> SetPrimary(id)
{
return await new CustomErrorHandler(() =>
this.BuildUrl(id).AppendSegment("Primary")
.PostJsonAsync(null, cancellationToken)
.ReceiveJson<Notification>())()).ExecuteAsync();
}
If I were to do something like that I would have to remember to use the error handler on all endpoint, when I feel like there's a better way to invert the control. (Alternatively, I could generate dummy interface and have the wrapping logic there but that arises the same issues as manually adding the calls).
How can I wrap all of the calls with error handler logic?
c# .net rest architecture
c# .net rest architecture
edited Nov 13 at 0:36
asked Nov 12 at 3:13
johnny 5
7,028123671
7,028123671
I am a bit confused by the presented code as it does not provide enough context for me to have a clear picture of what it is suppose to be doing. That said however, you mentioned pipeline and the middleware pattern came to mind. If you have a pipeline that manages requests then you can insert a middleware early in the pipeline that was satisfy the behavior you seek
– Nkosi
Nov 12 at 3:23
similar to how message handlers are used in Web API
– Nkosi
Nov 12 at 3:28
@nkosi thanks for your response I’ll check that out
– johnny 5
Nov 12 at 3:35
You appear to be using Flurl. these might be of some interest to you. flurl.io/docs/configuration and flurl.io/docs/extensibility
– Nkosi
Nov 13 at 1:48
1
not if you apply it globally.
– Nkosi
Nov 13 at 1:56
|
show 4 more comments
I am a bit confused by the presented code as it does not provide enough context for me to have a clear picture of what it is suppose to be doing. That said however, you mentioned pipeline and the middleware pattern came to mind. If you have a pipeline that manages requests then you can insert a middleware early in the pipeline that was satisfy the behavior you seek
– Nkosi
Nov 12 at 3:23
similar to how message handlers are used in Web API
– Nkosi
Nov 12 at 3:28
@nkosi thanks for your response I’ll check that out
– johnny 5
Nov 12 at 3:35
You appear to be using Flurl. these might be of some interest to you. flurl.io/docs/configuration and flurl.io/docs/extensibility
– Nkosi
Nov 13 at 1:48
1
not if you apply it globally.
– Nkosi
Nov 13 at 1:56
I am a bit confused by the presented code as it does not provide enough context for me to have a clear picture of what it is suppose to be doing. That said however, you mentioned pipeline and the middleware pattern came to mind. If you have a pipeline that manages requests then you can insert a middleware early in the pipeline that was satisfy the behavior you seek
– Nkosi
Nov 12 at 3:23
I am a bit confused by the presented code as it does not provide enough context for me to have a clear picture of what it is suppose to be doing. That said however, you mentioned pipeline and the middleware pattern came to mind. If you have a pipeline that manages requests then you can insert a middleware early in the pipeline that was satisfy the behavior you seek
– Nkosi
Nov 12 at 3:23
similar to how message handlers are used in Web API
– Nkosi
Nov 12 at 3:28
similar to how message handlers are used in Web API
– Nkosi
Nov 12 at 3:28
@nkosi thanks for your response I’ll check that out
– johnny 5
Nov 12 at 3:35
@nkosi thanks for your response I’ll check that out
– johnny 5
Nov 12 at 3:35
You appear to be using Flurl. these might be of some interest to you. flurl.io/docs/configuration and flurl.io/docs/extensibility
– Nkosi
Nov 13 at 1:48
You appear to be using Flurl. these might be of some interest to you. flurl.io/docs/configuration and flurl.io/docs/extensibility
– Nkosi
Nov 13 at 1:48
1
1
not if you apply it globally.
– Nkosi
Nov 13 at 1:56
not if you apply it globally.
– Nkosi
Nov 13 at 1:56
|
show 4 more comments
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
Based on what has been shown so far, the endpoints appear to be using Flurl.
Under the hood that framework uses HttpClient
, which should provide an extensibility point to take advantage of the request pipeline.
According to documentation, you should be able to configure a global setting to achieve the desired behavior.
For example
I have a large number of these endpoints and I would like to run some additional code before each one of these calls
e.g For example if my oauth token is invalid I would want to get a new access token and retry the request automatically.
private async Task HandleOAuthAsync(HttpCall call) {
//...check response and if token expired perform some action or trigger some event
}
//...
//register globally
FlurlHttp.Configure(settings => settings.AfterCallAsync = HandleOAuthAsync);
There is even the ability to go down to the client level for more direct access to the client or message handlers if so desired.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Based on what has been shown so far, the endpoints appear to be using Flurl.
Under the hood that framework uses HttpClient
, which should provide an extensibility point to take advantage of the request pipeline.
According to documentation, you should be able to configure a global setting to achieve the desired behavior.
For example
I have a large number of these endpoints and I would like to run some additional code before each one of these calls
e.g For example if my oauth token is invalid I would want to get a new access token and retry the request automatically.
private async Task HandleOAuthAsync(HttpCall call) {
//...check response and if token expired perform some action or trigger some event
}
//...
//register globally
FlurlHttp.Configure(settings => settings.AfterCallAsync = HandleOAuthAsync);
There is even the ability to go down to the client level for more direct access to the client or message handlers if so desired.
add a comment |
up vote
1
down vote
accepted
Based on what has been shown so far, the endpoints appear to be using Flurl.
Under the hood that framework uses HttpClient
, which should provide an extensibility point to take advantage of the request pipeline.
According to documentation, you should be able to configure a global setting to achieve the desired behavior.
For example
I have a large number of these endpoints and I would like to run some additional code before each one of these calls
e.g For example if my oauth token is invalid I would want to get a new access token and retry the request automatically.
private async Task HandleOAuthAsync(HttpCall call) {
//...check response and if token expired perform some action or trigger some event
}
//...
//register globally
FlurlHttp.Configure(settings => settings.AfterCallAsync = HandleOAuthAsync);
There is even the ability to go down to the client level for more direct access to the client or message handlers if so desired.
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Based on what has been shown so far, the endpoints appear to be using Flurl.
Under the hood that framework uses HttpClient
, which should provide an extensibility point to take advantage of the request pipeline.
According to documentation, you should be able to configure a global setting to achieve the desired behavior.
For example
I have a large number of these endpoints and I would like to run some additional code before each one of these calls
e.g For example if my oauth token is invalid I would want to get a new access token and retry the request automatically.
private async Task HandleOAuthAsync(HttpCall call) {
//...check response and if token expired perform some action or trigger some event
}
//...
//register globally
FlurlHttp.Configure(settings => settings.AfterCallAsync = HandleOAuthAsync);
There is even the ability to go down to the client level for more direct access to the client or message handlers if so desired.
Based on what has been shown so far, the endpoints appear to be using Flurl.
Under the hood that framework uses HttpClient
, which should provide an extensibility point to take advantage of the request pipeline.
According to documentation, you should be able to configure a global setting to achieve the desired behavior.
For example
I have a large number of these endpoints and I would like to run some additional code before each one of these calls
e.g For example if my oauth token is invalid I would want to get a new access token and retry the request automatically.
private async Task HandleOAuthAsync(HttpCall call) {
//...check response and if token expired perform some action or trigger some event
}
//...
//register globally
FlurlHttp.Configure(settings => settings.AfterCallAsync = HandleOAuthAsync);
There is even the ability to go down to the client level for more direct access to the client or message handlers if so desired.
answered Nov 13 at 2:53
Nkosi
108k16113182
108k16113182
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53255516%2fdelay-building-of-a-request%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I am a bit confused by the presented code as it does not provide enough context for me to have a clear picture of what it is suppose to be doing. That said however, you mentioned pipeline and the middleware pattern came to mind. If you have a pipeline that manages requests then you can insert a middleware early in the pipeline that was satisfy the behavior you seek
– Nkosi
Nov 12 at 3:23
similar to how message handlers are used in Web API
– Nkosi
Nov 12 at 3:28
@nkosi thanks for your response I’ll check that out
– johnny 5
Nov 12 at 3:35
You appear to be using Flurl. these might be of some interest to you. flurl.io/docs/configuration and flurl.io/docs/extensibility
– Nkosi
Nov 13 at 1:48
1
not if you apply it globally.
– Nkosi
Nov 13 at 1:56