I found that to prevent the cache when you update SWF versions
openmeetings possible, adding the parameter in the creation of
SWFObject.
now SWFObject is created in this way (see index.jsp):
var so = new SWFObject ( "main.lzx.swf8.swf", "lzapp", "100%", "100%",
"8", "# ffffff");
let's add the name of SWF object parameter, which will vary with each
installation of an application (for simplicity I pointed out the
revision number in svn):
var so = new SWFObject("main.lzx.swf8.swf?rev=2115", "lzapp", "100%",
"100%", "8", "#ffffff");
revision number in the name of the object at the next installation
will be modified and the browser will load the SWF object from a site,
rather than from the cache. What actually solves potential problem
with the caching of SWF.
imho that was a good idea to add it to the build system. What do you
think about this?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"OpenMeetings User" group.
To post to this group, send email to openmeetings-user@googlegroups.com
To unsubscribe from this group, send email to
openmeetings-user+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/openmeetings-user?hl=en
-~----------~----~----~----~------~----~------~--~---
