Changeset 0178e11 in Lumiera

Timestamp:

2026-03-14T02:36:15Z (6 weeks ago)

Author:

Ichthyostega <prg@…>

Branches:

dev/play

Children:

9be75c9

Parents:

d91ca67a

git-author:

Ichthyostega <prg@…> (13/03/26 21:35:46)

git-committer:

Ichthyostega <prg@…> (14/03/26 02:36:15)

Message:

BufferProvider: simplify OutputSlot implementation structure

The old implementation relied on two layered APIs:
one for the client and one for the implementer of
the Allocation state. This is logically sound, yet
clumsy in terms of design, since the internal API
turns out to be void of actual meaning.

It seems possible to eliminate this confusing structure
by a clear separation of implementation realms

• the mechanics of connection state management
• the actual implementation of the connection

The first can be provided as generic template subclass,
while the latter should be confined entirely into the
implementation of the Connection interface.

Doing so requires to keep each part of the implementation
strictly focused onto its purpose — something I obviously
was not able to see at the time when writing this old
implementation, notably because I was completely guided
and driven by the test/dummy implementation without
considering how an actual implementation of
low-level data output would work.

(No files)