| title | IFileKey::GetCacheName Method |
|---|---|
| description | Learn how the IFileKey::GetCacheName method returns the name of the global file cache. |
| ms.date | 10/07/2016 |
| ms.assetid | 1d0a3a67-6f6c-d0d7-f29f-19e9a40871a3 |
Returns the name of the global file cache.
PCWSTR GetCacheName(
VOID
) const; This method takes no parameters.
A pointer to a constant null-terminated Unicode string that contains the name of the global file cache. The default is FILE_CACHE_NAME (described in IIS Caching Constants).
The cache name represents the unique name of a cache where file data may be stored and retrieved.
IFileKey implementers are responsible for memory management with this data; therefore, IFileKey implementers that use dynamic memory allocation must release or call delete on the PCWSTR pointer when it is no longer needed.
Classes that directly implement the IFileKey interface should not override the default GetCacheName method, because the FILE_CACHE_NAME value instructs clients that are holding an IHttpCacheKey pointer that the pointer may be safely downcast to an IFileKey pointer.
IFileKey implementers are responsible for memory management with this data; therefore, IFileKey clients must not release or call delete on the returned PCWSTR pointer when this data is no longer needed. Furthermore, clients must not cast this data to a pointer that is not a const or change the state of the memory referenced by this PCWSTR, because an access violation will be thrown or the data will become invalid.
Interfaces that extend the IFileKey interface may override the GetCacheName method. However, the value returned must not collide with currently defined values, including those returned from the IHttpTokenKey::GetCacheName or IUriKey::GetCacheName method.
The following code example demonstrates how to create a global module that listens for GL_CACHE_OPERATION and GL_CACHE_CLEANUP events and then writes the GetCacheName information to the Event Viewer.
Caution
[!INCLUDEiisver] generates a large number of events in the Event Viewer. To avoid a log overflow error in a production environment, you should generally avoid writing cache information to the event log. For demonstration purposes, this code example writes an entry to the Event Viewer in debug mode only.
[!code-cppIFileKey#2]
The above code writes a new event to the Event Viewer, where the Data box contains a string similar to the following.
IFileKey::GetCacheName: FILE
Your module must export the RegisterModule function. You can export this function by creating a module definition (.def) file for your project, or you can compile the module by using the /EXPORT:RegisterModule switch. For more information, see Walkthrough: Creating a Request-Level HTTP Module By Using Native Code.
You can optionally compile the code by using the __stdcall (/Gz) calling convention instead of explicitly declaring the calling convention for each function.
| Type | Description |
|---|---|
| Client | - IIS 7.0 on [!INCLUDEwinvista] - IIS 7.5 on Windows 7 - IIS 8.0 on Windows 8 - IIS 10.0 on Windows 10 |
| Server | - IIS 7.0 on [!INCLUDEwinsrv2008] - IIS 7.5 on Windows Server 2008 R2 - IIS 8.0 on Windows Server 2012 - IIS 8.5 on Windows Server 2012 R2 - IIS 10.0 on Windows Server 2016 |
| Product | - IIS 7.0, IIS 7.5, IIS 8.0, IIS 8.5, IIS 10.0 - [!INCLUDEiisexp75], [!INCLUDEiisexp80], [!INCLUDEiisexp100] |
| Header | Httpcach.h |