> >> So there's no need to hesitate if you can already do (1) today. Let's > >> face it, you have been very successful and there are rather a lot of > >> users who have already gotten past (2) :) > > > > Okay, I'm kinda tired of that argument. Just beacuse you say something > > isn't possible, doesn't mean we can't make it work anyway. If you believe > > they're divergent, stop saying that they're divergent and prove it with > > examples. However I'd rather spend my time writing features than > > pretending to know if a theoretical patch will work or not. > > > > We want to work towards a system that can encompass a replacement for > > "stats cachedump". If we can design something which generates sflow as a > > subset, that'll be totally amazing! We can even use your patches as > > reference for creating a core shipped plugin. > > > > If people want to use sflow today, they can apply your patches and use it. > > As is such with open source. > > > > -Dormando > > > I didn't say it wasn't possible.... but never mind all that. A > core-shipped plugin would be great. Let me know if there's anything I > can do to help.
That was more strongly worded than I intended, I apologize; I don't agree that it's worth rushing. Not "rushing" is why we haven't already settled on TOPKEYS the way it is. I don't really intend to throw something else in there immediately.
