• DataContract serialization implementation (WCF)
• Workitem: Socket closure on shutdown
• Major bug in fallback logic (special thanks to Christian Weyer from thinktecture - http://www.thinktecture.com/staff/christian)
• Replicated caching and distributed caching versions contains now a flag with an online / offline status.
• Extended logging - trace socket pool bahaviour when shared cache runs as debug installation. Use SysteInternals DbgView to view how the socket pool act.
• Client and server socket pool configurations (SocketPoolValidation, SocketPoolTimeout, SocketPoolMinAvailaleSize)

Information about how to configure client and replicated server socket pools can be found here:

• Replicated server socket pool configuration: http://www.sharedcache.com/cms/default.aspx?pg=e9acfe54-2da7-4515-924a-e46723921764#Release%203.0.5.1
• Client socket pool configuration: http://www.sharedcache.com/cms/default.aspx?pg=adc4b470-11a5-4e87-8d06-8ff0e4fd3b05#release%203.0.5.1

tips & tricks:
if you install the server on the same server we suggest to use different locations for the log files. eg:
Server: h:\app_logs\server\
Client: j:\app_logs\client\

Consider firewall configurations: if you have communication problems check your firewall file: C:\WINDOWS\pfirewall.log

• RegExRemove exit to early
• memory leakage in caching service
• Unhardcode job_install batch files
• Server Expiry Check - return null instead of the object
• Request Extension of Expiration Date without Read
• MultiDelete not working?
• Cache Failing to Function Under Heavy Load
• Poll Data From Replicated Servers doesn’t work properly
• validate client replication section
• CHM File Not Usable (All Links Broken)
• Enterprise Library 4.0 ICacheManager support
• Rep / Dist - Server node key extension with online / offline flag

• Important: The Service name changed from "indeXus.Net" to "SharedCache.com"
• adaption of logging pattern, makes it easier to open log files within office environment
• integrated disc output caching, not used so far but preparations are done for next release.
• changes done on winservice controller for easier handling
• protocol extension to receive clr version, sharedcache version and when an item will be expiered
• added snk file so WinServericeCommen can be placed in GAC
• created configuration sections
• usage of various hashing algorithms
• a new registration project have been added to the solution, this winform post some registration details to our web-server upon registration
• a new web-service is available for registration within the version project
• user need to registrate before they can use the new network family version with a lot of enhancements for handling cache
• First tests are working fine to persist full cache are running successfully
• //COM.Formatters.Serialization.FileSerialize(LocalCache, @"C:\cache.bin");
• //_cache = COM.Formatters.Serialization.FileDeSerialize(@"C:\cache.bin");
• added new icon for notify (main logo is now used)
• updated all script files in case C:\Windows is located at a different place then default value
• updated references to new webservice
• renamed app logging in event viewer from indexus.net to shared cache
• added an option for Time To Live
• upgraded all project to .net framework 3.5

• Option 1: Receive all keys on a specific host (if you work locally you can simple pass null as parameter).
• Option 2: Receive statistic information from a specific host.

• if you install the server on the same server we suggest to use different locations for the log files.

• if you have communication problems check your firewall file: C:\WINDOWS\pfirewall.log

• Upon startup we make now a version check and do not invoke automatically server stats.

• Environment Helpers

• Shared Cache CLR Check returns any CLR Version where shared cache is installed.
  

• A useful helper to ensure which hashing algorithm you are able to use.

• Take advantage of the new Network Overview which queries all cache nodes in real time

Abstract

indeXus.Net SharedCache is a high-performance, distributed caching system. Although application-neutral, it's commonly used to speed up dynamic Web applications by alleviating database load. indeXus.Net SharedCache runs as a distributed windows service on every web and / or application server farm to cache data objects in memory out of process. Your stored objects can be accessed from any of your servers in your farm.

Download

https://www.codeplex.com/Release/ProjectReleases.aspx?ProjectName=SharedCache

Release Date

• March, 14th 2008

Release Number (first official release)

• 2.0.3.270 - This is a release and not a pre_release.

Release Documentation

• http://doc.sharedcache.com/

Release Changes:

• Removed all server dependency on appSetting config section
• Removed all client dependency on appSetting config section
• Client performance improvements
• Server performance improvements
• Client Connection Pool Fail-over for replicated caching
• usage of #if Tracing #if Debug compilation statements
• Updated Installer
• Updated Notify network overview and Stats calls
• Usage of custom thread pool for server to server communication
• Client Test Application menu modifications
• Cache Lock based now on bulkObject and not on typeof(Cache)
• Cache-Cleanup takes usage of Dictionary instead of Lists
• Removed all unused Constants
• Cleanup Code comments which was not necessary
• Multi Get / Add / Remove Operations
• Bulk Operations are removed
• removed third party SharpZipLib and integrated all necessary code
• refactored several classes (CacheUtil.cs / IndexusMessage.cs / CacheException.cs) for easier tracing we use WinServiceCommon -> Handler -> Unique.cs for a process wide unique ID - used only for tracing purposes.
• Removed all needed Console.WriteLine() statements or added them into #if DEBUG compilation statement
• Added Get / Delete operations based on regular expressions
• Commented all Unit tests - we started to create a new set of tests which are working differently.

.Net Cache Provider extensions

• the provider contains now two additional options

  • Option 1: Receive all keys on a specific host (if you work locally you can simple pass null as parameter).
  • Option 2: Receive statistic information from a specific host.

tips & tricks:

• if you install the server on the same server we suggest to use different locations for the log files.

eg.

Server: h:\app_logs\server\
client: j:\app_logs\client\

Firewall
if you have communication problems check your firewall file: C:\WINDOWS\pfirewall.log