CODEWITHSUNDEEP
javascriptstylesheetlotus-dominoxpagescache-expiration
Thomas Adrian
Thomas Adrian

Reputation: 3636

How to force update of design changes to clients using xPages?

I am bulding a webpage using xPages and I am making constant changes to script and design, this include both server and client javascript , stylesheet and image changes.

Each time I change a javascript or stylesheet I want to see my changes in the webbrowser and I also want my users to get the latest changes when they access the webpage.

I know I can use Shift-Reload, or CTRL-reload and clear my webbrowser cache. and I also know that I can change the objects expiration date, but I want a smoother and better controlled way to do this.

Looking for any kind of best practice for doing this.

Thanks

Thomas

Upvotes: 0

Views: 3278

Answers (9)

jBoive
jBoive

Reputation: 1299

Adding to Ferry's answer and your comment;

Instead of "?dummy=randomvalue", you can use "?version=2.1". So it will be cached but when you change design, you can just increase the version.

There's a problem with this approach as some proxy servers won't cache anything with query params. Better to rename the file directly, adding date or version number to it. It will always work.

To disable caching temporarily use Fiddler2. It's easy to enable and disable in one place across any web client. As well as added benefits for the http request tracking features.

Upvotes: 1

Ramkumar
Ramkumar

Reputation: 842

Why do not we use the window.location.reload()...

Which does the same like ctrl+F5

It reloads the page, which is similar to context.reloadpage

Upvotes: 0

Thomas Adrian
Thomas Adrian

Reputation: 3636

I did found another solution by putting my css and js in a theme it is easy to just rename the files.

as described here http://goo.gl/vFTii

Upvotes: 0

Sean Cull
Sean Cull

Reputation: 503

NEwbs answer is a good one but it is useful to note that in Firefox there is a very useful plug in called "web developer" from Chris Pederick that allows you to disable the cache.

http://chrispederick.com/work/web-developer/

The other really useful one is Firebug which is just amazing - It makes any HTML work much easier

https://addons.mozilla.org/en-US/firefox/addon/firebug/

Upvotes: 0

jjtbsomhorst
jjtbsomhorst

Reputation: 1667

maybe you could look at how domino can control caching of url's.

http://www.ibm.com/developerworks/lotus/library/ls-resp_head_rules/

Upvotes: 0

Newbs
Newbs

Reputation: 1632

In the xsp.properties file for the application or on the server for server wide use you can set xsp.application.forcefullrefresh=true. The xsp.properties file documentation says:

# Application refresh # When this property is set to true, then a full application refresh is requested when # the design of a class changes (means that all the data are discarded in scopes).

# xsp.application.forcefullrefresh=false

The new XSP Portable Command Guide says "This property was introduced in Notes/Domino 8.5.3. It is set to false by default and is particularly useful during the development phase of an XPages application."

I have not fully tested this behavior but it sounds promising. You could/should of course only set it to true WHILE you make the changes. once stable, set it back.

/Newbs

Upvotes: 5

Serdar Basegmez
Serdar Basegmez

Reputation: 3365

Adding to Ferry's answer and your comment;

Instead of "?dummy=randomvalue", you can use "?version=2.1". So it will be cached but when you change design, you can just increase the version.

Upvotes: 0

RoyRumaner
RoyRumaner

Reputation: 769

The way I am reading this question is that you want every change you make to appear immediately on the client's browser or client. Are you really sure you want to do this? It sounds like you are not doing any testing so any typos, bugs, crashes, etc will be passed on to your users. Sounds like a bad plan to me. I hope I am wrong and that you are using a template and pushing only your fully tested changes up to an production version instead of making the changes in the production version.

I would just put out a schedule of when changes are going to be pushed up to production and let the users reload their browser or client at that time. Either that or do it during off hours and when they next log on, they get the newest changes.

Upvotes: 0

Ferry Kranenburg
Ferry Kranenburg

Reputation: 2635

To fully disable any caching add url + '"?dummy=" + @Unique();' to every url to javascript or image files...

Upvotes: 0

Related Questions