cubicweb #1056022 enhance support for distributed config [deprecated]

  1. deal with multiple repository config: we should be able to know they are instances of the same application (cf elo/apycot_elo + multisource pb) -> I think we can play with pyro ns hierarchy: application has an id (eg :cubicweb.elo) which is a pyro-ns group, various instances being registerd under this group. We could also automatically deal with events propagation between instances using this feature
  2. have persistent web session. That would greatly enhance multiple all-in-one instances configuration. Also that would ease web session handling: no more need to handle in memory session cleanup, could simply be done by a hook with a much bigger cleanup session time.
done in<not specified>
load left0.000
closed by<not specified>