We should consider making the update method public. At the moment we are trying to prevent the user from "doing any harm". But maybe one would like to calculate fluxes over a specific face after each time step and instead of having to build new local objects, maybe he would like to just store it and only update it. For problems considering several types of transport processes this would be a lot faster. In this case we should still look at:
-
remove (now) obsolete friendship between ElementFluxVariablesCache and CCLocalJacobian