Re: [Jack-Devel] transport rolling + new slow-sync client

PrevNext  Index
DateFri, 10 Jun 2011 10:55:19 -0400
From Paul Davis <[hidden] at linuxaudiosystems dot com>
ToDan Muresan <[hidden] at gmail dot com>
Cc[hidden] at jackaudio dot org
In-Reply-ToDan Muresan [Jack-Devel] transport rolling + new slow-sync client
Follow-UpPaul Davis Re: [Jack-Devel] transport rolling + new slow-sync client
Follow-UpDan Muresan Re: [Jack-Devel] transport rolling + new slow-sync client
On Fri, Jun 10, 2011 at 10:49 AM, Dan Muresan <[hidden]> wrote:
> Hi,
>
> I was wondering what happens if the transport is already Rolling, and
> a new slow-start client activates itself? Does Jack transition from
> Rolling to Starting and wait for the new client to complete syncing? I
> don't see that transition in the diagram -- and without it I don't
> understand how a slow-start client could reliably synchronize with an
> already-rolling transport...

that's correct. it cannot. it would have to request a transport stop
(which of course, any client may do), and then optionally restart the
transport.
PrevNext  Index

1307717735.28050_0.ltw:2,a <BANLkTin8tUC0iV6O3pDVX2Z0gKn1Fz_rqw at mail dot gmail dot com>