Mobile Module - Caching

Does anybody know how Component level caching works with Livesite Mobile Module? IN Livesite, the generted HTML output gets cached for a component and for any request, results are served from the cached.

Whenever mobile module gets integrated with Livesite, does the component need to be No-Cache to serve dynamic version of the content from server (based on the device type) or does the component somehow cache different version of component HTML output if caching is on?

If component has to be set No-Cache, then is it not performance impact as a lot of components will need to work without caching considering customer would want to show hide lot of components based the device type.

TS/LS 7.5

TIA

Find more posts tagged with

Comments

interDev

Any takers?

Rick Poulin

interDev wrote:
If component has to be set No-Cache, then is it not performance impact as a lot of components will need to work without caching considering customer would want to show hide lot of components based the device type.

That's pretty much the "gotcha" when using server-side UA detection. Either your performance drops, or your memory usage increases (for all the variations you need to cache).

You may be in uncharted territory with your current issue. I don't know very many organizations that are using LS Mobile, and I haven't gotten to that level of detail with it myself. Based on how LiveSite component caching works, I don't know how the user agent string could possibly appear within the cache key, because the set of possible values is on the order of a few thousand (assuming you only stick to "known" values), and there's no way you'd want to cache that many variations of the same component. But like I said, haven't looked into it.

interDev

Thanks Rick, Agree with your explaination but I wanted to check if somebody has seen actual module behavoir.