hm, this way you can do it today, but it is not so
effective, imho
And the best thing: You don't even need Yukon for it.
Cache invalidation future can be configured in SQL
Server 7/2000 using aspnet_regsqlcache.exe command line
tool.
Hi,
2 quick questions:
If I used WinForm rather than ASP.NET then the
application in question would be getting a live
notification from Yukon and I could handle it right
there on the spot? For my application, I would require
very timely response to any changes in the database.
Also, If the user of the application is only watching
certain rows in a table of a database, such as those
rows matching his/her userID, would that user only get
an notification if only those certain rows got updated?