Reconsidering Your Priorities

Cross-posting from my RTI blog:

What sometimes takes more time to get used to is that, when you’re deploying your application with RTI inside, there are no daemons or servers, so there are no queues to prioritize. You don’t need the solution, because the problem doesn’t exist. Messages go on the network in the order in which you call write() (in the DDS API, or send() / publish() in the JMS API), because we send them in the calling thread. And on the receiving side, if you take delivery of your data in a listener callback, you’ll get it immediately after it comes out of the operating system’s socket buffer. There’s no blocking or context switching required.

Read the whole post here.