×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hmmm... is there any way to detect that a message is a duplicate? For
example, does each message have a transaction ID number in it, so that a
duplicate could be detected (same ID occurs twice).
If so, I'd suggest leaving the message in the buffer, and when you
handle the response for the next transaction, just read and ignore any
transaction ids you've already handled.
That way, you don't end up waiting for duplicated data that might never
come.
But, if there's no way to detect whether you have a duplicate or not,
and every second counts in this app, then I'd suggest trying to fix the
problem at it's source.
On 1/28/2011 11:54 AM, hockchai Lim wrote:
The reason I want to use non-blocking is because speed is import for this
app. Waiting for even 1 sec might be too long. From what you are saying,
it seems like I just have to live with this out-of-sync possibility.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
