Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Yannick Smits 321 posts 718 karma points
    May 07, 2010 @ 10:29
    Yannick Smits
    0

    Compared to built in caching

    I was under the assumption that caching was built in to umbraco already. Could you elaborate on how it is different than built in caching? Is umbraco only caching on macro level and this package on page level?

  • Tobias Neugebauer 52 posts 93 karma points
    May 07, 2010 @ 11:51
    Tobias Neugebauer
    1

    Hi!

    Yes you are totally correct! If you switch to developer -> Cache Browser you are able to see what umbraco stores into the cache this is mainly internal stuff e.g. (as you mentioned) macros.

    The OutputCaching package caches on page level which can save some round trips on the server.

    If you think of the ASP.Net pipline there are several steps which take place for each and every request that hit the server:

    1. BeginRequest

    2. AuthenticateRequest

    3. AuthorizeRequest

    4. ResolveRequestCache (Caching hooks in here...)

    5. AquireRequestState

    6. PreRequestHandlerExecute

    7. …Handler Execution…

    8. PostRequestHandlerExecute

    9. ReleaseRequestState

    10. UpdateRequestCache (...and here)

    11. EndRequest

    Whith this module installed when a request hits the server it will check (in step 4) if the request is cachable (defined in the settings) and checks if there is a version in the cache. If it finds one it sends the cached data back to the client before the heavy processing happens. If there is no cached version it will duplicate all the data send to the client and stores that into the cache (in step 10) when all the processing is done.

    I hope i could make myself clear about this module :)

    Cheers,

    Toby

Please Sign in or register to post replies

Write your reply to:

Draft