On Tue, 26 May 2015, Nicolas Dichtel wrote:
Yes, I think we have to be pragmatic: you have now someone who have
spend a lot of time to write and propose a patch which implements the
single-daemon option and which does not block the multi-daemon option.
It's probably not the perfect solution for all scenarii, but it's done, it
works and it does not block any other options.
Sure. It may also has costs in terms of churn, and adding another
configuration to support. So it'd good to see what the level of churn is,
and discuss the UI/config issues, and get a better sense of where
the balance lies, before committing.
Be good to have others pitch in too on opinion, either way. :)
Just very generally, not talking about this particularly, but I'd strongly
encourage design discussions to be had on list /before/ any substantive
implementation work on major new directions. Up-front design and
co-ordination here on quagga-dev obviously becomes more important as more
people work on Quagga. It's much easier for everyone then, than after.
regards,
--
Paul Jakma [email protected] @pjakma Key ID: 64A2FF6A
Fortune:
Minnie Mouse is a slow maze learner.
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
