Now I have a working setup for a `BufferProxyAdaptor`. Unfortunately this is still confusingly complex. This is due to my intention to build a generic template, that can be configured with a policy to invoke arbitrary callbacks, whenever one of the passed-through buffers transitions through its lifecycle. * we need to configure the `BufferProviderSetup` to use our specific implementation classes * and the second one of these, our `BufferStore` implementation needs to invoke the callbacks |
||
|---|---|---|
| .. | ||
| application | ||
| steam | ||
| vault | ||
| DIR_INFO | ||