What is the difference between a request and a command?









up vote
1
down vote

favorite
1












Just a simple question:
what is the difference between a request and a command in protocols like HTML or SMTP?

Can it be that requests await a response?

Or that one is from the client side and the other from the server side?

Thanks in advance!










share|improve this question





















  • Most succinctly a request may encompass multiple commands. Ex Http request contains many headers
    – Jay
    Nov 11 at 20:38










  • @Jay Can you give an example in smtp?
    – Ishailg
    Nov 11 at 20:46










  • Tried, let me know is that's not clear
    – Jay
    Nov 11 at 20:54














up vote
1
down vote

favorite
1












Just a simple question:
what is the difference between a request and a command in protocols like HTML or SMTP?

Can it be that requests await a response?

Or that one is from the client side and the other from the server side?

Thanks in advance!










share|improve this question





















  • Most succinctly a request may encompass multiple commands. Ex Http request contains many headers
    – Jay
    Nov 11 at 20:38










  • @Jay Can you give an example in smtp?
    – Ishailg
    Nov 11 at 20:46










  • Tried, let me know is that's not clear
    – Jay
    Nov 11 at 20:54












up vote
1
down vote

favorite
1









up vote
1
down vote

favorite
1






1





Just a simple question:
what is the difference between a request and a command in protocols like HTML or SMTP?

Can it be that requests await a response?

Or that one is from the client side and the other from the server side?

Thanks in advance!










share|improve this question













Just a simple question:
what is the difference between a request and a command in protocols like HTML or SMTP?

Can it be that requests await a response?

Or that one is from the client side and the other from the server side?

Thanks in advance!







network-programming






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 11 at 20:29









Ishailg

103




103











  • Most succinctly a request may encompass multiple commands. Ex Http request contains many headers
    – Jay
    Nov 11 at 20:38










  • @Jay Can you give an example in smtp?
    – Ishailg
    Nov 11 at 20:46










  • Tried, let me know is that's not clear
    – Jay
    Nov 11 at 20:54
















  • Most succinctly a request may encompass multiple commands. Ex Http request contains many headers
    – Jay
    Nov 11 at 20:38










  • @Jay Can you give an example in smtp?
    – Ishailg
    Nov 11 at 20:46










  • Tried, let me know is that's not clear
    – Jay
    Nov 11 at 20:54















Most succinctly a request may encompass multiple commands. Ex Http request contains many headers
– Jay
Nov 11 at 20:38




Most succinctly a request may encompass multiple commands. Ex Http request contains many headers
– Jay
Nov 11 at 20:38












@Jay Can you give an example in smtp?
– Ishailg
Nov 11 at 20:46




@Jay Can you give an example in smtp?
– Ishailg
Nov 11 at 20:46












Tried, let me know is that's not clear
– Jay
Nov 11 at 20:54




Tried, let me know is that's not clear
– Jay
Nov 11 at 20:54












1 Answer
1






active

oldest

votes

















up vote
0
down vote



accepted










Similar to http, smtp requests can contain multiple commands e.g. the TLS command to enabled encryption



E.g. HELO, BYE



Ftp is similar to Smtp, where a single connection (request) exchanges multiple commands (PASV... EXIT) before the connection is closed.



The main difference is the request response for http can usually be visualized as 1 request to 1 response however when you look at how the TLS encryption is applied over http you then see similar commands being exchanged between client and server before the final response is returned to the client.



In short http separates the noise of the commands by encompassing them into the header portions of the request and response.



An example of http commands without encryption would be chucked transfer encoding where the server send a part of the response after the headers in chunks which must be put back together at the client side.






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%2f53252936%2fwhat-is-the-difference-between-a-request-and-a-command%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
    0
    down vote



    accepted










    Similar to http, smtp requests can contain multiple commands e.g. the TLS command to enabled encryption



    E.g. HELO, BYE



    Ftp is similar to Smtp, where a single connection (request) exchanges multiple commands (PASV... EXIT) before the connection is closed.



    The main difference is the request response for http can usually be visualized as 1 request to 1 response however when you look at how the TLS encryption is applied over http you then see similar commands being exchanged between client and server before the final response is returned to the client.



    In short http separates the noise of the commands by encompassing them into the header portions of the request and response.



    An example of http commands without encryption would be chucked transfer encoding where the server send a part of the response after the headers in chunks which must be put back together at the client side.






    share|improve this answer


























      up vote
      0
      down vote



      accepted










      Similar to http, smtp requests can contain multiple commands e.g. the TLS command to enabled encryption



      E.g. HELO, BYE



      Ftp is similar to Smtp, where a single connection (request) exchanges multiple commands (PASV... EXIT) before the connection is closed.



      The main difference is the request response for http can usually be visualized as 1 request to 1 response however when you look at how the TLS encryption is applied over http you then see similar commands being exchanged between client and server before the final response is returned to the client.



      In short http separates the noise of the commands by encompassing them into the header portions of the request and response.



      An example of http commands without encryption would be chucked transfer encoding where the server send a part of the response after the headers in chunks which must be put back together at the client side.






      share|improve this answer
























        up vote
        0
        down vote



        accepted







        up vote
        0
        down vote



        accepted






        Similar to http, smtp requests can contain multiple commands e.g. the TLS command to enabled encryption



        E.g. HELO, BYE



        Ftp is similar to Smtp, where a single connection (request) exchanges multiple commands (PASV... EXIT) before the connection is closed.



        The main difference is the request response for http can usually be visualized as 1 request to 1 response however when you look at how the TLS encryption is applied over http you then see similar commands being exchanged between client and server before the final response is returned to the client.



        In short http separates the noise of the commands by encompassing them into the header portions of the request and response.



        An example of http commands without encryption would be chucked transfer encoding where the server send a part of the response after the headers in chunks which must be put back together at the client side.






        share|improve this answer














        Similar to http, smtp requests can contain multiple commands e.g. the TLS command to enabled encryption



        E.g. HELO, BYE



        Ftp is similar to Smtp, where a single connection (request) exchanges multiple commands (PASV... EXIT) before the connection is closed.



        The main difference is the request response for http can usually be visualized as 1 request to 1 response however when you look at how the TLS encryption is applied over http you then see similar commands being exchanged between client and server before the final response is returned to the client.



        In short http separates the noise of the commands by encompassing them into the header portions of the request and response.



        An example of http commands without encryption would be chucked transfer encoding where the server send a part of the response after the headers in chunks which must be put back together at the client side.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Nov 11 at 21:02

























        answered Nov 11 at 20:53









        Jay

        2,55611825




        2,55611825



























            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%2f53252936%2fwhat-is-the-difference-between-a-request-and-a-command%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







            這個網誌中的熱門文章

            How to read a connectionString WITH PROVIDER in .NET Core?

            In R, how to develop a multiplot heatmap.2 figure showing key labels successfully

            Museum of Modern and Contemporary Art of Trento and Rovereto