I was wondering how/if the umbraco.config xml file is cached. Since ive noticed that if we delete the umbraco.config the content is still accessable and when we restart the solution it will be renegrated.
The reason why im asking is because we have a huge project that we are in the starting phase of, and i think we could use a similar approach for it. (and its ofc being built upon umbraco but some of the data is being stored outside of data)
Im gussing its being chached in memory somehow or what ? and how is it done
Yes, I believe your understanding is correct: umbraco.config is automatically generated from and represents all the nodes (content) in your database as an XML structure.
If this file is deleted, Umbraco will serve content directly from the source (database), and will also re-generate this XML.
I believe the XML is cached in server memory (probably HttpRuntimeCache, haven't dug into the code to verify), and it is this use of caching which helps make Umbraco as performant as it is - and also resilient to temporary disconnections, where the database becomes unreachable or otherwise inaccessible.
question: how is the umbraco.config XML cached ?
Hey there :)
I was wondering how/if the umbraco.config xml file is cached. Since ive noticed that if we delete the umbraco.config the content is still accessable and when we restart the solution it will be renegrated.
The reason why im asking is because we have a huge project that we are in the starting phase of, and i think we could use a similar approach for it. (and its ofc being built upon umbraco but some of the data is being stored outside of data)
Im gussing its being chached in memory somehow or what ? and how is it done
Hi Rasmus,
Yes, I believe your understanding is correct: umbraco.config is automatically generated from and represents all the nodes (content) in your database as an XML structure.
If this file is deleted, Umbraco will serve content directly from the source (database), and will also re-generate this XML.
I believe the XML is cached in server memory (probably HttpRuntimeCache, haven't dug into the code to verify), and it is this use of caching which helps make Umbraco as performant as it is - and also resilient to temporary disconnections, where the database becomes unreachable or otherwise inaccessible.
Regards,
Allen
Thx Allen for your comment.
yeah thats also the way i was thinking it :) Thx
is working on a reply...