Log in Register

Login to your account

Username *
Password *
Remember Me

Create an account

Fields marked with an asterisk (*) are required.
Name *
Username *
Password *
Verify password *
Email *
Verify email *
Captcha *

Blog

 

Multicache V1.0.0.3 to feature a stronger tweaker -expected release in Jun 15 Featured

The next version of multicache V1.0.0.3 will be launched in Jun 15. This version will feature a stronger Javascript tweaker that will include quirks in scripts like jQuery libraries with an encoded script tag. Currently in development, this section will undergo a transformation with every release until V1.0.1 wherein a fiddle type tweaker will manifest allowing developers to adhoc slip and slide code between various load-sections of the webpage. 
  • 184
  • Last modified on Thursday, 09 April 2015 10:32

Related items

Leave a comment

Make sure you enter the (*) required information where indicated. HTML code is not allowed.

highlights

  • Multicache V1.0.0.3 to feature a stronger tweaker -expected release in Jun 15
    Multicache V1.0.0.3 to feature a stronger tweaker -expected release in Jun 15

    The next version of multicache V1.0.0.3 will be launched in Jun 15. This version will feature a stronger Javascript tweaker that will include quirks in scripts like jQuery libraries with an encoded script tag.

    Currently in development, this section will undergo a transformation with every release until V1.0.1 wherein a fiddle type tweaker will manifest allowing developers to adhoc slip and slide code between various load-sections of the webpage. 

  • Knowing for certain that a page has been retrieved from cache
    Knowing for certain that a page has been retrieved from cache

    If it becomes necessary to ascertain with confidence the fact that a page being tested for load time has indeed been retrieved from cache,

    Multicache config has an option under advanced simulation called 'simulation parsing'. This option when set to urlquery will generate loadinstructions which are visible in the query url, this is also referred to as simulation id. In this mode, if we parse a query fragment called 

    ?cachehit=true

    Then a log is generated every time cache is queried but there was no response , thereby signifying a cache miss. So, all that requires to be done, is add the query fragment to the test url and ensure advanced simulation is set to 'urlquery'. The log can be then referred to in the category 'multicache_simulation_cachepageworkaround'