> > "Erik Bray" <[EMAIL PROTECTED]> writes: > >> On Thu, Nov 13, 2008 at 8:28 AM, Emmanuel Blot <[EMAIL PROTECTED]> >> wrote: >>> >>>> Yes, I was wondering the other day if it would be possible to change >>>> the >>>> syncing algorithm, by having it run "in the background", and while it >>>> is >>>> running, to get data from the repository directly for requests. >>> >>> I think that the few cases where a manual resync are required is not >>> worth adding the complexity of managing a background thread. >>> These manual resync usually follow admin tasks, so IMHO the current >>> implementation is good enough. >> >> If anything, spawning a separate process to do it would make more >> sense than a thread. But I agree that manual resyncs are uncommon >> enough that it's not worth the effort. > > There is one use case that might warrant the background resync. > > - server hosts multiple trac environments > - all environments have their respective TRAC_ADMINs > - server has no TRAC_ADMIN shell accounts > (or TRAC_ADMINs that are lost at the command-line :-() > > Just a thought,
As a general design philosophy, Trac isn't meant ot be used with 0 shell access. Very little, yes, but not none. I think if someone wants to develop a nice reusable system for Trac vhosting that would be great, but we should solve that externally from Trac itself for now (either a plugin, or some other system that embeds Trac). --Noah --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
