caching tags

[何塞]

Hi guys,

I was wondering if there is a way to cache tags with a dispatcher pointing to an author instance? This is for AEM 6.1

We have a lot of tags and they all get loaded automatically when a user visits:

1) http://localhost:4502/assets.html/content/dam

The tags are loaded as part of the Search panel on that interface. I looked around and while the tags are ultimately an html unordered list, the entire search panel is embedded and rendered as part of that request. Since the request does not have an extension the dispatcher won't cache it, which makes sense since we probably don't want to cache the contents of "/content/dam" or the contents of any other path underneath it.

But we probably would want to cache the search panel, since it's the same across all paths and views.

I noticed that a request to:

2) http://localhost:4502/libs/dam/gui/content/commons/sidepanels/search.html

Will render the actual search panel. Is there a way to have the request in 1) embed the html from 2)? This way then the URL in 2) could be cached in the dispatcher.

Thanks in advance for all ideas, comments, or suggestions

何塞。

[smacdonald2008]

THis is being discussed with internal ppl. I will post back the answer.

[smacdonald2008]

While I am waiting to hear back - i recommend that you watch this great webinar on Dispatcher from last July:

Scott's Digital Community: Ask the AEM Community Experts for July 2017

You may find it useful on this subject.

[kautuk_sahni]

Jörg Hoh​ need your help here!!

[oswaldo_huezo]

Hi Scott,

Thanks for your reply. The link you sent is actually for something related to Dynamic Media. Can you please send me the link to the Dispatcher discussion?

Thanks a bunch,

何塞。

[smacdonald2008]

Here is Dispatcher ATCE -- ATACE July 25 2017 Advanced AEM Dispatcher Configurations

[Jörg_Hoh · Accepted solution]

Hi,

The dispatcher can only cache complete responses. It cannot cache only a part of the reponse or embed a cached file into the response body of a different request. So technically it is not possible to embed the response body of

http://localhost:4502/libs/dam/gui/content/commons/sidepanels/search.html

into the response body of

http://localhost:4502/assets.html/content/dam

if the system is not built that way (it isn't). Can you check if the performance issue exists on 6.3 as well and raise a ticket for this?

Jörg

[何塞]

Hi Jörg,

It seems AEM 6.3 uses lazy loading in its "Filters" section, so it won't have this issue. It will have performance issues however if you were to open the dialog with all the tags in it, as the "Filters" section, just like the Search panel, is part of the whole request that can't be cached.

Anyways, I'll open an improvement request ticket on my side.

Thanks a bunch!

何塞。