AEM 6.5.6 | How is AEM stiching the page? | Community
Skip to main content
A
Annie_Rose_Peter
Level 2
May 21, 2021
Solved

AEM 6.5.6 | How is AEM stiching the page?

  • May 21, 2021
  • 3 replies
  • 2622 views

When we create AEM editable templates and components as drag and drop , how does the AEM stitch the page on user-end/ browser ?  Is it called as an HTML page ? or each component and their content are separately called and stitched together in browser.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by VeenaVikraman

Hi @annie_rose_peter 

 

      This is a vast topic. I have tried to explain the Sling Resolution in one of my articles. Might be helpful. Please check https://www.linkedin.com/pulse/sling-resource-resolution-aem-part-1-veena-vikraman/ https://www.linkedin.com/pulse/sling-resource-resolution-aem-part-2-veena-vikraman/ 

 

Thanks

Veena

3 replies

Peter_Puzanovs
Community Advisor
Peter_PuzanovsCommunity Advisor
Community Advisor
May 21, 2021

Hi Annie,

 

This is very broad question. Can you narrow down a bit? Which part of the stitching of AEM are you interested in?

 

Regards,

Peter

 

    A
    Annie_Rose_PeterAuthor
    Level 2
    May 24, 2021
    Thanks Peter. The reason was load time of static templates were lower than dynamic editable templates . So was checking if the stiching is any diffrent in both type templeates
    Asutosh_Jena_
    Community Advisor
    Asutosh_Jena_Community Advisor
    Community Advisor
    May 22, 2021

    Hi @annie_rose_peter 

     

    When we create a page(HTML) in AEM from a template and add component on it by authoring different content the whole page is considered as an HTML page.

    Now When the request is made to the perticular page from browser side, the call is made to the server where the HTML page is rendered by calling the components on it. Now each of the component will have their own HTL (HTML templating Language) which will be executed at the server side and it will generate the content in the form of HTML.

    Same HTML content is served to the browser here by caching the content at the dispatcher (caching and load balancing). If the same page request is made in future again the page will be served from the cache to reduce the load on the publish instance. Now there are some other considerations as well like if the content is going to be static or dynamic. If it;s going to be a static content the whole page will be cached whereas if the content is going to be dynamic content the content will be served from the publish instance.

     

    Thanks!

      VeenaVikraman
      Community Advisor
      VeenaVikramanCommunity AdvisorAccepted solution
      Community Advisor
      May 22, 2021

      Hi @annie_rose_peter 

       

            This is a vast topic. I have tried to explain the Sling Resolution in one of my articles. Might be helpful. Please check https://www.linkedin.com/pulse/sling-resource-resolution-aem-part-1-veena-vikraman/ https://www.linkedin.com/pulse/sling-resource-resolution-aem-part-2-veena-vikraman/ 

       

      Thanks

      Veena

        A
        Annie_Rose_PeterAuthor
        Level 2
        May 24, 2021

        Thanks Veena , that was helpful . The reason why i started looking into these are because a facing an issue where load time of static templates were lower than dynamic media editable templates . Is there any other factors affecting this because as you have mentioned sling will resolve according to the JCR node structure , which will be similar in both cases .

        Terms & ConditionsAccessibility statement

        Loading footer...