CefSharp中如何为ResourceHandler传递单浏览器实例专属上下文参数？

Absolutely, you can set up a unique context (like your database connection service instance) for each CefSharp browser instance—this is a clean way to ditch the messy global state you're currently using. Let's walk through a straightforward implementation:

1. Create Your Custom Context Class #

First, define a class to hold your database connection and any other instance-specific data:

public class BrowserDbContext
{
    // Replace with your actual database service/connection
    public IDatabaseConnectionService DbConnection { get; }

    public BrowserDbContext(IDatabaseConnectionService dbConnection)
    {
        DbConnection = dbConnection;
    }
}

2. Attach Context to Individual Browser Instances #

You have two solid options here:

Option A: Subclass ChromiumWebBrowser #

Create a custom browser class with a dedicated property for your context—this is explicit and type-safe:

public class ContextAwareBrowser : ChromiumWebBrowser
{
    public BrowserDbContext InstanceContext { get; set; }

    public ContextAwareBrowser(string url) : base(url) { }
}

Option B: Use the Built-in Tag Property #

If you don't want to subclass, leverage the existing Tag property (it's designed for storing arbitrary instance data):

// When creating your browser
var browser = new ChromiumWebBrowser("https://your-app-url");
browser.Tag = new BrowserDbContext(yourDbConnectionService);

3. Access the Context in Your ResourceHandler #

In your RequestHandler (or ResourceHandlerFactory), you can retrieve the context from the IWebBrowser parameter passed to methods like GetResourceHandler:

For the Custom Subclass Approach: #

public class CustomRequestHandler : RequestHandler
{
    protected override IResourceHandler GetResourceHandler(IWebBrowser chromiumWebBrowser, IBrowser browser, IFrame frame, IRequest request)
    {
        var contextBrowser = chromiumWebBrowser as ContextAwareBrowser;
        if (contextBrowser?.InstanceContext != null)
        {
            // Pass the context to your custom ResourceHandler
            return new DbBackedResourceHandler(contextBrowser.InstanceContext);
        }

        // Fallback to default handling if no context exists
        return base.GetResourceHandler(chromiumWebBrowser, browser, frame, request);
    }
}

For the Tag Property Approach: #

protected override IResourceHandler GetResourceHandler(IWebBrowser chromiumWebBrowser, IBrowser browser, IFrame frame, IRequest request)
{
    var dbContext = chromiumWebBrowser.Tag as BrowserDbContext;
    if (dbContext != null)
    {
        return new DbBackedResourceHandler(dbContext);
    }

    return base.GetResourceHandler(chromiumWebBrowser, browser, frame, request);
}

4. Use the Context in Your Custom ResourceHandler #

Modify your ResourceHandler to accept the context via its constructor, then use it to fetch data:

public class DbBackedResourceHandler : ResourceHandler
{
    private readonly BrowserDbContext _dbContext;

    public DbBackedResourceHandler(BrowserDbContext dbContext)
    {
        _dbContext = dbContext;
    }

    public override bool ProcessRequest(IRequest request, ICallback callback)
    {
        // Use your context to query the database
        var data = _dbContext.DbConnection.FetchDataForRequest(request.Url);
        
        // Convert data to a response (e.g., JSON, HTML)
        var responseBytes = Encoding.UTF8.GetBytes(JsonSerializer.Serialize(data));
        Stream = new MemoryStream(responseBytes);
        MimeType = "application/json";
        ResponseLength = responseBytes.Length;

        callback.Continue();
        return true;
    }
}

Key Notes to Avoid Issues #

• Lifecycle Management: Make sure to dispose of your BrowserDbContext when the browser instance is destroyed (hook into the BrowserClosed event) to prevent memory leaks.
• Dependency Injection: If you're using DI, you can inject your database service directly into the custom browser class or context for cleaner setup.
• Type Safety: The subclass approach is preferred if you want compile-time checks, while Tag is quicker for simple scenarios.

内容的提问来源于stack exchange，提问作者ekalchev