> > and the problem would be what?
>
> That the first user (or admin) that triggers a resync - without even
> noticing it - will end up with a hard-to-understand "timeout error" in
> his browser, with no other information to help him diagnose the issue.
A stack trace and a timeout are certainly not the only options. One
could start the resync in another thread or process and display an
informative message ("Due to a recent configuration change, we're
busily resynchronizing with the repository. Unfortunately, some
functionality may be unavailable until we have finished."), or even
bypass the cache and go directly to the repository during the resync.
Certainly this is a better experience for end-users.
The opposing viewpoint is that the only people who can cause this are
people who can do something about it: admins. Resyncs are partial
outages, and if you're doing something that requires one, you need to
message your users appropriately, possibly scheduling it in advance.
Resyncs only happen in fairly rare circumstances when you're making
major disruptive changes.
I should note that a feature being a better experience for end-users
doesn't necessarily mean you should implement it. There is some
possibility that admins will do resyncs more frequently if they know
that they're handled automatically. Resyncs are inherently disruptive
to users, even if we do a good job of making them automated. A good
admin will try to avoid the sorts of disruptive changes that lead to
them. Also, it may be that this feature would just be nice to have,
while other features are critically important. That is, this feature
may be low priority, in which case the developers should be working on
higher priority stuff.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
