internal/pipewire: implement client generation footer
All checks were successful
Test / Create distribution (push) Successful in 38s
Test / Sandbox (push) Successful in 2m26s
Test / Hakurei (push) Successful in 3m16s
Test / Hpkg (push) Successful in 4m13s
Test / Sandbox (race detector) (push) Successful in 4m22s
Test / Hakurei (race detector) (push) Successful in 5m12s
Test / Flake checks (push) Successful in 1m29s
All checks were successful
Test / Create distribution (push) Successful in 38s
Test / Sandbox (push) Successful in 2m26s
Test / Hakurei (push) Successful in 3m16s
Test / Hpkg (push) Successful in 4m13s
Test / Sandbox (race detector) (push) Successful in 4m22s
Test / Hakurei (race detector) (push) Successful in 5m12s
Test / Flake checks (push) Successful in 1m29s
This corresponds with the core generation footer and seem to be the only other possible footer type. Signed-off-by: Ophestra <cat@gensokyo.uk>
This commit is contained in:
@@ -81,6 +81,16 @@ type FooterCoreGeneration struct {
|
||||
RegistryGeneration Long `json:"registry_generation"`
|
||||
}
|
||||
|
||||
// The FooterClientGeneration indicates to the server what is the last
|
||||
// registry generation number the client has processed.
|
||||
//
|
||||
// The client shall include this footer in the next message it sends,
|
||||
// after it has processed an incoming message whose footer includes a
|
||||
// registry generation update.
|
||||
type FooterClientGeneration struct {
|
||||
ClientGeneration Long `json:"client_generation"`
|
||||
}
|
||||
|
||||
// A CoreInfo event is emitted by the server upon connection
|
||||
// with the more information about the server.
|
||||
type CoreInfo struct {
|
||||
|
||||
Reference in New Issue
Block a user