×
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.
Musselman, Paul wrote:
Alan--
Not an answer to your question per se...
We had an application that time stamped all of the transactions in its
log file. But they came in so fast that multiple records had the same
time stamp! The solution was to have the application delay for a
fraction of a second between writes so the time stamps were unique.
There are various ways to skin this cat. In most cases, job number and
timestamp can't be beat. This is especially true if you have a called
program to write the record. In the (nearly impossible) situation where
you have a process that might write two records at the exact same time,
you simply compare the timestamp with the previous timestamp and if they
match, loop getting the timestamp until they don't match any more. This
is a foolproof mechanism that only adds the overhead of a compare and a
very rare delay.
I'm not sure what's required for a GUID, but my sense is that it's
system wide it requires interprocess synchronization and thus could
become a performance issue, especially as the number of processes rises.
Joe
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
