Scott Guthrie announced formally during the Mix09 keynote that Velocity will be shipping with ASP.NET 4.0

*************
Daniel Chait (March 18, 2009 - 11:42am) wrote in his blog:

Scott Guthrie announced formally during the Mix09 keynote that Velocity will be shipping with ASP.NET 4.0. Big news for the distributed cache market!
*************
hope microsoft is gonna ship caching provider they announced some time ago in LA.

Poker and Shared Cache

do you like poker ? I do, checkout how a custom version of shared cache helps to run a poker game: read ivan's post why he decided to use shared cache instead of velocity: http://www.ivanbondy.com/Blog/archive/2009/03/16/microsoft-velocity-out-shared-cache-in-.aspx

SharedCache Version: 3.0.5.1 - Release Notes

Abstract
SharedCache is a high-performance, distributed caching system. Although application-neutral, it's commonly used to speed up dynamic applications by alleviating database load. 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, 9th 2009
Release Number: 3.0.5.1
Release Documentation: http://doc.sharedcache.com/ (is not updated now - coming soon)

3.0.5.1 contains:

• 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 about firewall configurations: if you have communication problems check your firewall file: C:\WINDOWS\pfirewall.log