On Fri, 11 Dec 2015, Donald Sharp wrote:
From: Dinesh G Dutt <[email protected]>
Currently, modifications to route maps do not affect already processed
routes; they only affect new route updates. This patch addresses this
limitation.
That's a pretty short commit message, for a fairly involved patch. It'd
be nice to say a bit more about the UI changes and the approach chosen.
E.g., it seems this reprocesses route-maps after a timer expires. That
seems like it has significant UI implicatoins. What are the pros/cons of
a timer versus finding some kind of event - e.g. the user typing 'exit'
and the command node transitioning back to 'ENABLE_NODE'?
I had a con. call with Donald a good few months ago on this, and I
thought we were agreed a more explicit user-driven event would be better
(at least for upstream as the default)?
regards,
--
Paul Jakma | [email protected] | @pjakma | Key ID: 0xD86BF79464A2FF6A
Fortune:
Hotels are tired of getting ripped off. I checked into a hotel and they
had towels from my house.
-- Mark Guido
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
