Ensures all CSS files are loaded before showing the injected fragment / Simple resource management #26
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Two main changes:-
e.g. When navigating from my applications 'welcome' page to 'user control panel' only a single fragment needs to be updated rather than a full page load. Therefore I perform an ajax request to get the html of the required fragment. With the above changes, the response of this request was reduced down to around 200ms from about 800ms. You can now essentially specify all required resources needed to render a fragment without repeating requests under any circumstance (ajax request or full page load).
NOTE: Please look at the full file from the latest 'commit' as it took me a while to get to grips with the way pull requests work in github. My apologies.