[Feature Request] In the L1/L2 cache, the L2 PUT and DELETE operations should be async fire and forget

[bgavrilMS]

As per discussion with SharePoint cache owners, they have gotten a perf boost by executing L2 operations in 'fire and forget" mode. Particularly for Redis, PUT operations take a long time. The L1 cache will have been updated anyway.

Should only be done if L1 is enabled.

[jmprieur]

How is this achieved, @bgavrilMS ?
By removing the await and adding a pragma disable?

[bgavrilMS]

No, you'd do

Task.Run(async () => ...)

Have a look at this helper function that MSAL uses to perform refresh_in operation in the background: https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/blob/master/src/client/Microsoft.Identity.Client/Internal/Requests/SilentRequestHelper.cs#L70

[jennyf19]

We considered doing this before, but we discussed with @henrik-me and went with a re-try on failure. We'd have to see if they have set the re-try callback and then do fire and forget.

[bgavrilMS]

I was thinking about that as well. Maybe the re-try can be part of the fire and forget logic

Task.Run(async() => 
    bool success = await WriteToRedis();
    if (!success) 
       await WriteToRedis();
    );

[jennyf19]

closing as duplicate of #1047

[jennyf19]

Included in the [1.22.0 release](https://github.com/AzureAD/microsoft-identity-web/releases/tag/1.22.00