Leopard iCal "Calendar Cache" subscription refresh bug persists in 10.5.3

Question

The 10.5.3 Leopard update does NOT fix the infamous Leopard iCal "Calendar Cache" bug, as discussed in http://discussions.apple.com/thread.jspa?messageID=6660830 .
This bug, introduced with Leopard, prevents iCal from picking up modifications to events on subscribed calendars. The workaround is to delete "~/Library/Calendars/Calendar Cache" and then refresh calendars. The file deletion can be done automatically by a login Automator script as suggested by a contributor to the thread linked above.
This to me is one of the most embarrassing bugs introduced with Leopard. It has high impact (prevents use of iCal in an enterprise setting) while appearing to be a very simple bug and thus most likely very easy to fix.

Answer 1

Hmm, I did not get the "Calendar Cache could not be moved" message when I updated to 10.5.3.
The bug I'm referring to is different. It is a persistent bug in all Leopard versions to date. It prevents iCal from detecting modifications to subscribed calendars.
For example, say you subscribe to a baseball-game schedule. The organizers decide to change the date of a game in the calendar server. But you arrive at the field on the original date, surprised that you are the only one there. Why? Leopard iCal relies on stale cached information EVEN WHEN EXPLICITLY TOLD TO REFRESH SUBSCRIPTIONS.
The only way around it is to delete the "Calendar Cache" file and then ask for an iCal refresh ON A REGULAR BASIS since otherwise you don't know if subscribed events have been modified or not.
Or, use SunBird.
I don't think this has anything to do with the "file cannot be moved" error some folks are apparently seeing as part of the update to 10.5.3. That probably deserves its own thread?