[Deploying Sakai] OAE UI Caching

Sean DeMonner demonner at umich.edu
Thu Aug 18 03:14:26 PDT 2011

I'm pretty certain that making networking changes every time we need to roll out a new release is not going to fly at my institution. Thanks for bringing this up so we can investigate further.


Sean DeMonner, Director, Teaching & Learning, ITS
3350 Duderstadt Center, University of Michigan, (734) 615-9765

On Aug 18, 2011, at 4:36 AM, Daniel Parry <daniel at caret.cam.ac.uk> wrote:

> Hi,
> Sent this to UI dev but wondering if it might be better sent here:
> So we've been trying to figure out what to do with the UI,
> caching, and handling application upgrades. As the code currently
> stands, it seems like we'd need to tell all our users to "clear
> their cache" every time we do an upgrade, which will potentially
> be a helpdesk problem eventually with aggressive browser caching
> proxies, etc.
> I think there is some thought going on as to how to solve this
> from a UI perspective[0], though this is seeming quite a tricky
> problem and the thread seemed to stop at the end of July? If a
> (magic) fix doesn't come through in time for our go live and
> upgrades, we're kicking around the idea of using new CNAMEs every
> time we do a code upgrade and putting in appropriate redirects
> from the old CNAMEs:
> http://v1.service.org
> http://v2.service.org
> etc
> Thus, browsers will see the new host and refetch the code every
> time we upgrade. Not ideal from an operations perspective, but
> probably doable especially if upgrades don't fly in thick and
> fast.
> Wondered if any other institutions have been brainstorming on this
> at all or have any thoughts on the matter, or even some magic :)?
> Best wishes,
> Daniel
> [0]
> http://collab.sakaiproject.org/pipermail/sakai-ui-dev/2011-July/010168.html
> -- 
> --| Daniel Parry: daniel at caret.cam.ac.uk. www.caret.cam.ac.uk/ |--
> "Snakes. Why did it have to be snakes?"
> [Indiana Jones, "Raiders of the Lost Ark"]
> _______________________________________________
> production mailing list
> production at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/production
> TO UNSUBSCRIBE: send email to production-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

More information about the production mailing list