Is there a way to cashing 'standard' CSHTML5 libraries at Client side ?

Please post public support tickets here. Note: for private support tickets, please send an email to support@cshtml5.com instead.
Sesztak
Posts: 172
Joined: Fri Jun 24, 2016 2:19 am

Is there a way to cashing 'standard' CSHTML5 libraries at Client side ?

Postby Sesztak » Wed Aug 03, 2016 12:41 pm

Dear JS-Support,
Is there a way to cashing 'standard' CSHTML5 libraries at Client side to save bandwidth and speed-up web-site start-up time ?

Background:
your CSHTML5 'standard' libraries size (actually beta 9.0):
-3.52 MB at output folder root,
-1.46 MB at Libraries subfolder
----
sum : 4.98 MB !

It takes a lot of time to download this libs.

Is there any way to cash (e.g. store with isolatedlocal storage) these js libs at the client side to speed up the web-site start-up?

Best Regards,
Thanks for your kind reply in advance,
Péter

Sesztak
Posts: 172
Joined: Fri Jun 24, 2016 2:19 am

Re: Is there a way to cashing 'standard' CSHTML5 libraries at Client side ?

Postby Sesztak » Thu Aug 04, 2016 3:15 am

Sorry,

cashing = cache (I misspelled).

Sesztak
Posts: 172
Joined: Fri Jun 24, 2016 2:19 am

Re: Is there a way to cashing 'standard' CSHTML5 libraries at Client side ?

Postby Sesztak » Thu Aug 04, 2016 4:28 am

Dear JS-Support,

Or are you using CACHE MANIFEST as mentioned in the following link already? :

https://developer.apple.com/library/ios ... orage.html

Or any other client side cache mechnanism already? like:
https://devcenter.heroku.com/articles/i ... he-headers

Is there any way to get more control about it ? -e.g. max. age / when it will expires. and/or Last-Modified response header?

Best Regards,
Thanks for your kind reply in advance,
Péter

Sesztak
Posts: 172
Joined: Fri Jun 24, 2016 2:19 am

Re: Is there a way to cashing 'standard' CSHTML5 libraries at Client side ?

Postby Sesztak » Fri Aug 05, 2016 6:12 am

Dear JS-Support,

We have checked CSHTML5 produced site by F12 : Chrome Developer mode: Audits function, the result:
(see attached picture)
the caching is not optimal:

CSHTML5_CacheProblem.JPG
CSHTML5_CacheProblem.JPG (97.81 KiB) Viewed 5777 times


Leverage browser caching (26)
-Some resources are missing a cache expiration. Resources that do not specify an expiration may not be cached by browsers, like:
fastclick.js
getStackTrace.js
velocity.js
-The following resources are explicitly non-cacheable. Consider making them cacheable if possible:
(small note: I'm sure that you do it because of development progress / changing betas probably.)
JSIL.js
Polyfills.js
mersenne.js
JSIL.Core.js
JSIL.Host.js
JSIL.Browser.js
JSIL.Browser.Audio.js
JSIL.Browser.Loaders.js
JSIL.Browser.Touch.js
JSIL.Core.Types.js
JSIL.Core.Reflection.js
JSIL.References.js
JSIL.Unsafe.js
JSIL.PInvoke.js
JSIL.Bootstrap.js
JSIL.Bootstrap.Int64.js
JSIL.Bootstrap.DateTime.js
JSIL.Bootstrap.Text.js
JSIL.Bootstrap.Resources.js
JSIL.Bootstrap.Linq.js
JSIL.Bootstrap.Async.js
index.manifest.js

So is there a support from CSHTML5 to controll it without manual edit of cache headers ?

I'm sure with a small efforts from your side should be possible to control the cache headers from the developer point of view.
E.g. to add some UI or dedicated XML config files to control the standard used / "framework like" *.js files cache headers.

What do you think ?
Or can you recommend any other existing 3rd party solution to do that ?

Best Regards,
Thanks for your kind reply in advance,
Péter
Attachments
CSHTML5_CacheProblem.PNG
CSHTML5_CacheProblem.PNG (93.71 KiB) Viewed 5777 times


Return to “Technical Support”

Who is online

Users browsing this forum: No registered users and 2 guests

 

 

cron