How to achieve low latency of WCF server in publish-subscribe scenario? Specifically, clients subscribe to data and receive updates, latency in question is between data changing and client receiving the change? CPU, memory, bandwidth requirements are not important and can be high.
Basics are obvious: binary serialization, named pipes, etc. But does it makes sense, for example, to send data through always-connected stream? Or to send batch of updates as a single message to decrease RPC/header overhead?
May be there are some projects with code or interfaces available to use as example?