Even at ten seconds it’s a terrible design. The calendar data doesn’t change that rapidly. Was there any thought to the performance implications of all those extra requests? I also worry about potential blocking issues with the session object if multiple ajax requests are being fired concurrently.
The intent was to allow an auto refresh of the calendar screen. If you can supply a better design that would be greatly appreciated. I guess we should provide a way of turning it off (sorry for the issues) I will add a global to turn it off and change the timing to be 1, 5, or 10 min’s .
The “refresh” icon on each tab will refresh the window. Maybe we should just make that larger and add a tool tip?
Instead of an explicit refresh button, having the calendar autorefresh on an event like “focus or mouseover” of the calendar window would save the user a click. This way if the auto refresh rate is turned down to a few minutes, the user will still see changes by others if they are idle in a reasonable time frame, and when the are actively reengage with the window it will reflect the immediate state.
As an aside, the new “week view” doesn’t serve the same purpose as the old version did. The user should be able to at a glance see all the appointments for the week so they can easily pick an open slot during the week.