On 08/02/2010 11:15 AM, Hiers, David wrote:
If you need uniqueness, you probably need to do it yourself.
Agreed, and would be my preferred solution, except that when integrating disparate network elements that all have the common requirement to discern individual message series, but whose "programmatic" environments vary substantially in their capabilities. Rolling my own uniqueness works in a general-purpose programming environment where certain data structure primitives and library functions can be counted on, but not in more narrowly-conceived, domain-specific runtimes.
If it bugged us, we'd throw a mediator in front of the db to add a customer identifier to the callID or something. There's no problem that you can't solve with one more level of abstraction :)
Not always possible, especially in platforms we don't fully control. This may be an issue somewhat particular to what we do. -- Alex Balashov - Principal Evariste Systems LLC 1170 Peachtree Street 12th Floor, Suite 1200 Atlanta, GA 30309 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/