Web Component - Internal Browser Caching












11















Looking at Chrome's DevTools on http://www.polymer-project.org/docs/polymer/polymer.html I notice a few interesting, curious, and unexplained things:




  1. The browser caches the actual Polymer component, so subsequent <link rel="import" calls for the component don't need the server round trip.


  2. The browser caches those components as data URLs



enter image description here



enter image description here



Obviously, doing this makes loading cached components very fast (0 ms latency)



enter image description here



My questions




  1. How can I control the caching of my components so the cache can be invalidated if/when needed? (Looking at the spec at http://www.w3.org/TR/2014/WD-html-imports-20140311/ I see no mention of caching)


  2. Would it be worthwhile to break down my entire site structure into web components (aka, "widgets"), so the various parts of my site load this fast? Example, Instead of always serving the same layout with the same nav, I just deploy it with a <my-nav> component, with the data for the nav (where it'd make sense) is all contained within the component itself, thus requiring no interaction with the server once cached.







html caching browser-cache polymer web-component







share|improve this question





























    11















    Looking at Chrome's DevTools on http://www.polymer-project.org/docs/polymer/polymer.html I notice a few interesting, curious, and unexplained things:




    1. The browser caches the actual Polymer component, so subsequent <link rel="import" calls for the component don't need the server round trip.


    2. The browser caches those components as data URLs



    enter image description here



    enter image description here



    Obviously, doing this makes loading cached components very fast (0 ms latency)



    enter image description here



    My questions




    1. How can I control the caching of my components so the cache can be invalidated if/when needed? (Looking at the spec at http://www.w3.org/TR/2014/WD-html-imports-20140311/ I see no mention of caching)


    2. Would it be worthwhile to break down my entire site structure into web components (aka, "widgets"), so the various parts of my site load this fast? Example, Instead of always serving the same layout with the same nav, I just deploy it with a <my-nav> component, with the data for the nav (where it'd make sense) is all contained within the component itself, thus requiring no interaction with the server once cached.







    html caching browser-cache polymer web-component







    share|improve this question



























      11












      11








      11


      2






      Looking at Chrome's DevTools on http://www.polymer-project.org/docs/polymer/polymer.html I notice a few interesting, curious, and unexplained things:




      1. The browser caches the actual Polymer component, so subsequent <link rel="import" calls for the component don't need the server round trip.


      2. The browser caches those components as data URLs



      enter image description here



      enter image description here



      Obviously, doing this makes loading cached components very fast (0 ms latency)



      enter image description here



      My questions




      1. How can I control the caching of my components so the cache can be invalidated if/when needed? (Looking at the spec at http://www.w3.org/TR/2014/WD-html-imports-20140311/ I see no mention of caching)


      2. Would it be worthwhile to break down my entire site structure into web components (aka, "widgets"), so the various parts of my site load this fast? Example, Instead of always serving the same layout with the same nav, I just deploy it with a <my-nav> component, with the data for the nav (where it'd make sense) is all contained within the component itself, thus requiring no interaction with the server once cached.







      html caching browser-cache polymer web-component







      share|improve this question
















      Looking at Chrome's DevTools on http://www.polymer-project.org/docs/polymer/polymer.html I notice a few interesting, curious, and unexplained things:




      1. The browser caches the actual Polymer component, so subsequent <link rel="import" calls for the component don't need the server round trip.


      2. The browser caches those components as data URLs



      enter image description here



      enter image description here



      Obviously, doing this makes loading cached components very fast (0 ms latency)



      enter image description here



      My questions




      1. How can I control the caching of my components so the cache can be invalidated if/when needed? (Looking at the spec at http://www.w3.org/TR/2014/WD-html-imports-20140311/ I see no mention of caching)


      2. Would it be worthwhile to break down my entire site structure into web components (aka, "widgets"), so the various parts of my site load this fast? Example, Instead of always serving the same layout with the same nav, I just deploy it with a <my-nav> component, with the data for the nav (where it'd make sense) is all contained within the component itself, thus requiring no interaction with the server once cached.







      html caching browser-cache polymer web-component




      html caching browser-cache polymer web-component






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Oct 25 '14 at 12:38









      Hendrik Brummermann

      7,02522552




      7,02522552










      asked Jun 24 '14 at 15:10









      rodrigo-silveirarodrigo-silveira

      5,86644072




      5,86644072
























          1 Answer
          1






          active

          oldest

          votes


















          1














          It is easiest to control the cache on the server. You either need to provide eTags, change the date of the component file and use the Last-Modified header, or change the name of the file each time you change it.



          Another way to handle this is to create a Service Worker and have that manage the caching of your files.






          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',
            autoActivateHeartbeat: false,
            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%2f24390236%2fweb-component-internal-browser-caching%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









            1














            It is easiest to control the cache on the server. You either need to provide eTags, change the date of the component file and use the Last-Modified header, or change the name of the file each time you change it.



            Another way to handle this is to create a Service Worker and have that manage the caching of your files.






            share|improve this answer




























              1














              It is easiest to control the cache on the server. You either need to provide eTags, change the date of the component file and use the Last-Modified header, or change the name of the file each time you change it.



              Another way to handle this is to create a Service Worker and have that manage the caching of your files.






              share|improve this answer


























                1












                1








                1







                It is easiest to control the cache on the server. You either need to provide eTags, change the date of the component file and use the Last-Modified header, or change the name of the file each time you change it.



                Another way to handle this is to create a Service Worker and have that manage the caching of your files.






                share|improve this answer













                It is easiest to control the cache on the server. You either need to provide eTags, change the date of the component file and use the Last-Modified header, or change the name of the file each time you change it.



                Another way to handle this is to create a Service Worker and have that manage the caching of your files.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 25 '18 at 19:31









                IntervaliaIntervalia

                4,66211134




                4,66211134
































                    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.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f24390236%2fweb-component-internal-browser-caching%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

                    Create new schema in PostgreSQL using DBeaver

                    Image
                    0 At the beginning of my current job I had limited access to DB but recently my role is changed to superuser, admin, and owner. My colleague who was the previous DB admin is able to create a schema or change the permissions as there is a permission tab in the properties and he can change permissions by clicking easily. Would you please let me know how I can create schema and change permissions as well? Why his dbeaver looks different from me? He can easily right click on the schema folder on top of all schemas on the left side column and select create new schema while I do not have that, like the following picture I found on the internet. postgresql database-schema dbeaver share | improve this question
                    Read more

                    Deepest pit of an array with Javascript: test on Codility

                    Image
                    0 $begingroup$ This is the question from a Codility test, as a task in an interview: DeepestPit - problem description A non-empty zero-indexed array A consisting of N integers is given. A pit in this array is any triplet of integers (P, Q, R) such that: ·         0 ≤ P < Q < R < N; ·         sequence [A[P], A[P+1], ..., A[Q]] is strictly decreasing, i.e. A[P] > A[P+1] > ... > A[Q]; ·         sequence A[Q], A[Q+1], ..., A[R] is strictly increasing, i.e. A[Q] < A[Q+1] < ... < A[R]. The depth of a pit (P, Q, R) is the number min {A[P] − A[Q], A[R] − A[Q]}. For example, consider array A consisting of 10 elements such that: A[0] = 0 A[1] = 1 A[2] = 3 A[3] = -2 A[4] = 0 A[5] = 1 A[6] = 0 A[7] = -3 A[8] = 2 A[9] = 3 Triplet (2, 3, 4) is
                    Read more

                    Fotorealismo

                    Image
                    Guerrino Boatto, Venice's St. Barnaba Church and canal Il fotorealismo è un genere di pittura basato sull'uso di una o più fotografie dalle quali l'artista prende le informazioni necessarie da utilizzare poi nel processo della creazione dell'opera, in genere ad olio o ad acrilico, al fine di avere un aspetto finale il più simile possibile alla fotografia. Indice 1 Storia 2 Lista dei fotorealisti 3 Note 4 Voci correlate 5 Altri progetti Storia | Il fotorealismo è un movimento che nasce negli Stati Uniti d'America alla fine degli anni sessanta [1] sulla scia della Pop Art [2] [3] [4] , e insieme condividono il carattere reazionario verso la travolgente ascesa dei media, che alla metà del ventesimo secolo si trasforma in un fenomeno di massa talmente imponente da minacciare il valore dell'immagine nell'arte. [5] [6] Ne consegue così che, colto il gesto d'inizio che fu della Pop Art, i fotorealisti aprono ad un
                    Read more