[Mono-bugs] [Bug 49486][Maj] Changed - Cache expiration mechanism is not functional

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Sat, 8 Nov 2003 02:28:42 -0500 (EST)

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by jackson@ximian.com.


--- shadow/49486	2003-11-04 11:34:42.000000000 -0500
+++ shadow/49486.tmp.15193	2003-11-08 02:28:42.000000000 -0500
@@ -1,13 +1,13 @@
 Bug#: 49486
 Product: Mono/Class Libraries
 Version: unspecified
 OS: All
 OS Details: 
-Status: NEW   
+Status: RESOLVED   
+Resolution: INVALID
 Severity: Unknown
 Priority: Major
 Component: System.Web
 AssignedTo: gonzalo@ximian.com                            
 ReportedBy: yaronsh@mainsoft.com               
 QAContact: mono-bugs@ximian.com
@@ -54,6 +54,14 @@
 Created an attachment (id=5539)
 ------- Additional Comments From yaronsh@mainsoft.com  2003-10-09 09:36 -------
 The last attachment was the code behind...
+------- Additional Comments From jackson@ximian.com  2003-11-08 02:28 -------
+With mono items in the cache are expired every minute. They are also
+rounded up 1 minute so the max off time is 1:59. It looks like MS
+expires every minute on the minute so their max off time is 0:59. I
+dont see anything in the spec that guarantees an expire time to be
+called immediatly so I am going to mark as invalid. If you have some
+docs that say differently I will reopen.