All - I was planning on going over the some high level overview of where I see zebra going. https://docs.google.com/presentation/d/1SeDS5b-Wgmp-2T_9povfHscP6Xpaihff_xsx... thanks! donald
It took me a bit to understand that "Zebra" referred to the daemon, rather than the entire project :-)
This is a lot of work, no way it can be fit in by itself giving our work constraints Long Term goal of where we want to be Threading Allow more flexibility to handle route installation. Add ability for filters and additional modules to stack in slide 8. Consider something like route compression, how would we handle this in zebra
It seems to me that the right way forward is to convert to objects that *can* be enqueued and processed asynchronously, but to do all the work synchronously until the locking can be worked out. I've been reading about RUST... it could do so many nice things here :-( -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | network architect [ ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
Michael - That is one of the actual goals. There is just a lot of work to do to unwind code to get to that point. Evolution is going to take time. donald On Tue, Feb 6, 2018 at 7:42 PM, Michael Richardson <mcr@sandelman.ca> wrote:
It took me a bit to understand that "Zebra" referred to the daemon, rather than the entire project :-)
This is a lot of work, no way it can be fit in by itself giving our work constraints Long Term goal of where we want to be Threading Allow more flexibility to handle route installation. Add ability for filters and additional modules to stack in slide 8. Consider something like route compression, how would we handle this in zebra
It seems to me that the right way forward is to convert to objects that *can* be enqueued and processed asynchronously, but to do all the work synchronously until the locking can be worked out.
I've been reading about RUST... it could do so many nice things here :-(
-- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | network architect [ ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
participants (2)
-
Donald Sharp -
Michael Richardson