Push vs. pull model of dequeuing
Hi all, I wonder if anyone can comment on these two methods of dequeuing:
- push e.g. asynchronous notification of available messages (onAQNotification() ...).
- pull e.g. using DEQUEUE_WAIT_FOREVER wait option while dequeuing.
These two patterns are somewhat typical in message-oriented environments, but I miss any good reason to prefer a specific one in the context of AQ (such as performance).
I'm driving this subject in the context of jdbc only.
Comments are welcome.