Invalidating connection savin dating those you cant love and loving those you
Dispatcher caches the files again only when it recieves a client request for the page.
Deleting cached files ins this manner is appropraite for web sites that are not likely to receive simultaneous requests for the same page. This can be used to flush particular resources without invalidating other parts of the cache, like JSON data that is dynamically created and requires regular flushing independent of the cache (e.g.
representing data that is obtained from a third-party system to display news, stock tickers, etc.).
Issue an HTTP request that causes Dispatcher to delete cached files, and immediately retrieve and recache the file.
It turns out it was nothing to do with the NSXPCConnection but rather a misunderstanding about the Widget Life Cycle on my behalf.
From the documentation I thought that the today view would keep a 'snapshot' of my widgets state until the widget Perform Update With Completion Handler method completion handler was called with success. From what I can see the 'snapshot' is just used when the Today View is animating in (when the user pulls down the notification centre).
At this moment you should populate you widget with cached data (not from a web request).The request causes Dispatcher to eventually refresh the file in the cache as new content is published.Under certain circumstances performance gains can be made by transferring cache management from the authoring environment to a publishing instance.A simple way to cache the data is in user defaults. A slick app that supports automatic or manual queryset caching and automatic granular event-driven invalidation.