>
> I am not sure yet how the implementation in case of virtual tables
> fits into the overall picture of "pluggability".
Yeah, it was a goal of the design to make writing new types as easy as
possible, so having to wire up a new vtable for each new event type works
against that.
I'd be incline
Yes, limits are good, in case of a solution for virtual tables. I can
imagine that it will be use just for the sake of diagnostics what a
node is doing and so on and even we lift the limit to something like
1000, that is already a plenty to show a respective operator (as a
person) what a node does
Some input…
We don't need a CEP for this: Diagnostic Events already exists, as do
Virtual Tables. But if you want to take it to a CEP, that's to be
encouraged :)
Virtual Tables should remain virtual, i.e. they shouldn't be backed by
custom system_* tables solely for the sake of persisting the vir
