Provide a way to flush NetworkTables to the wire immediately about allwpilib HOT 8 OPEN

The rate restriction is there to prevent overloading the wifi at events. We do not want to provide a standard way to bypass it. I would be open to figuring out a behind the scenes way that turns it off for non-Rio (eg simulation) NT servers (this could be done with an ifdef).

from allwpilib.

Ok to just ifdef the existing flush() or do you want a separate flushNow()?

from allwpilib.

Actually, I'd need it not just for servers, but clients as well. Is there an acceptable/recommended way that the client could determine that it is talking to a non-RIO server?

from allwpilib.

@PeterJohnson we could use really-flush-immediately too, because we use NT for perishable coprocessor-to-rio data, and we trust the coprocessors to manage their own rates. we completely don't care about wifi. is there a standard way to do immediate client flushes like that?

from allwpilib.

You can immediately client flush, but it’s rate limited. Are you really sending data updates from coprocessors more often than every 5 ms?

from allwpilib.

no, we're really only concerned with latency, which is already pretty high, so it if were easy to save a few ms, that would be good.

from allwpilib.

So if you call NetworkTableInstance.Flush(), it will immediately flush to network, assuming it’s been at least 5 ms since the last time the network transmit happened.

from allwpilib.

ohhhh. we'll try that.

from allwpilib.