I took a session on “Caching Enhancements and Client Callback in ASP.NET Whidbey” last week in Bangalore .NET User Group. You can download the presentations from here
Caching Enhancements and Client Callback in ASP.NET Whidbey
Best part in this session was discussion on how to implement these feature in exisinting ASP.NET 1.x applications.
Few links related to session.
On Caching
- Caching Improvements in ASP.NET Whidbey
- Improved Caching in ASP.NET 2.0
- Implement Custom Cache Dependencies in ASP.NET 1.x
- Supporting Database Cache Dependencies in ASP.NET 1.x
On Client Callback
- Client Callbacks in ASP.NET Whidbey
In .Net framework 1.x, cookieless support was there only for sessions. But in whidbey, you can have forms authentication without the support of cookie's. You can enable it in machine.config or web.config similar to cookieless sessions,
<configuration>
<system.web>
<authentication mode="Forms">
<forms name=".MYASPXAuth"
loginUrl="login.aspx"
protection="All"
timeout="30"
defaultUrl="Default.aspx"
cookieless="UseUri"/>
</authentication>
</system.web>
</configuration>
When compared to cookieless property in session element, cookieless forms authentication property has more options. Following are the various options,
- UseUri: Authentication tickets will be stored in the URL itself. Similar to session state cookieless option.
- UseCookies: Default option, will use cookies for forms authentication.
- AutoDetect: It will automatically detect whether browser support cookies or not
- UserDeviceProfile:Chooses to use cookies or not based on the device profile settings in machine.config