Re: jack still broken
Steve Langasek <firstname.lastname@example.org> writes:
> On Fri, Sep 23, 2005 at 12:38:24PM -0500, Adam Heath wrote:
>> On Fri, 23 Sep 2005, Thomas Bushnell BSG wrote:
>> > Steve Langasek <email@example.com> writes:
>> > > How else do you handle the case of a library which implements a line
>> > > protocol (presumably Unix sockets, in this case), and that protocol has
>> > > changed incompatibly?
>> > You implement the new protocol on a new port, so that both the old and
>> > new jackd can be run at the same time.
>> No, you design the protocol from the beginning to have the first token be a
>> protocol version, followed by a magic number(which could be different per
> That doesn't make the new daemon any more compatible with the old clients if
> the code isn't kept around to implement the old protocol.
Right. New protocol versions should be implemented by new daemons, or
by daemons that can speak both protocols.
To see this done more or less right, examine ssh.