[Mono-bugs] [Bug 433483] Cache/CacheDependency's behaviour different from .NET' s implementation
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Fri Oct 10 03:44:47 EDT 2008
https://bugzilla.novell.com/show_bug.cgi?id=433483
User juraj at hotfeet.ch added comment
https://bugzilla.novell.com/show_bug.cgi?id=433483#c4
Juraj Skripsky <juraj at hotfeet.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #244300|0 |1
is obsolete| |
--- Comment #4 from Juraj Skripsky <juraj at hotfeet.ch> 2008-10-10 01:44:47 MDT ---
Created an attachment (id=244805)
--> (https://bugzilla.novell.com/attachment.cgi?id=244805)
cache.aspx - aspx test page
Hi Gonzalo, hi Marek,
thanks for the patch and the input!
Give me three or four more days and I'll have my patch ready that matches
NET's behaviour and eliminates CheckDependencies() completely. I will change
both CacheItem and CacheDependencies to have a list of CacheDependencies
tracking it. That way, we can recursively notify all interested parties
whenever a cache item is removed and/or a dependency has changed.
I'm attaching an extended test page. The output on .NET is the following:
Key 'Y1' removed (reason: DependencyChanged).
Key 'Z1' removed (reason: DependencyChanged).
Key 'X1' removed (reason: Removed).
=======
Key 'X2' removed (reason: Removed).
Key 'Z2' removed (reason: DependencyChanged).
Key 'Y2' removed (reason: DependencyChanged).
=======
Key 'Z2b' removed (reason: DependencyChanged).
Key 'X2b' removed (reason: Removed).
=======
Key 'X2c' removed (reason: Removed).
Key 'Z2c' removed (reason: DependencyChanged).
=======
Key 'X3' removed (reason: DependencyChanged).
=======
Key 'X4' removed (reason: DependencyChanged).
=======
=======
Key 'Y6' removed (reason: Removed).
Key 'X6' removed (reason: Removed).
Key 'Z6' removed (reason: DependencyChanged).
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the mono-bugs
mailing list