[Mono-bugs] [Bug 433483] New: Cache/CacheDependency's behaviour different from .NET' s implementation

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=433483


           Summary: Cache/CacheDependency's behaviour different from .NET's
                    implementation
           Product: Mono: Class Libraries
           Version: SVN
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sys.Web
        AssignedTo: mhabersack at novell.com
        ReportedBy: juraj at hotfeet.ch
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---


Created an attachment (id=244300)
 --> (https://bugzilla.novell.com/attachment.cgi?id=244300)
cache.aspx - aspx test page

Recipe:
=======
- start xsp2
- request http://localhost:8080/cache.aspx

Actual result:

Key 'X1' removed (reason: Removed).
=======
Key 'X2' removed (reason: Removed).
=======
=======


Expected result:

Key 'X1' removed (reason: Removed).
Key 'Z1' removed (reason: DependencyChanged).
Key 'Y1' removed (reason: DependencyChanged).
=======
Key 'Z2' removed (reason: DependencyChanged).
Key 'X2' removed (reason: Removed).
Key 'Y2' removed (reason: DependencyChanged).
=======
Key 'X3' removed (reason: DependencyChanged).
=======
Key 'X4' removed (reason: DependencyChanged).


(The order of X1/Y1/Z1 and X2/Y2/Z2 is random.)

Notes:
------
Test 1: Cache["Z1"] depends on Cache["Y1"], which in turn depends on
Cache["X1"]
Test 2: Cache["Z2"] and Cache["Y2"] both depend on Cache["X2"], with Z2's
dependency chained to Y2's dependency
Test 3: the dependency has (HasChanged == true) immediately after creation,
hence the cache item is removed on insertion
Test 4: must check the last modification time of the watched file
(see http://msdn.microsoft.com/en-us/library/ms150207.aspx for the semantics of
the "start" parameter)


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.