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?










share|improve this question
























  • 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















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?










share|improve this question
























  • 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













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?










share|improve this question















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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








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


















  • 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












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.






share|improve this answer





















    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    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

























    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.






    share|improve this answer

























      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.






      share|improve this answer























        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.






        share|improve this answer












        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.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 13 at 2:53









        Nkosi

        108k16113182




        108k16113182






























            draft saved

            draft discarded




















































            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.




            draft saved


            draft discarded














            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





















































            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







            Popular posts from this blog

            Guess what letter conforming each word

            Port of Spain

            Run scheduled task as local user group (not BUILTIN)