Re: Brands excluded from digicash beta

>Paul Robichaux (perobich@ingr.com) writes:

>Take a look at the process involved in clearing checks and you will soon
>see how it can get very strange.

If clearing sounds simple, may I suggest as a general rule of thumb
to look at the complexities involved with transaction management in
distributed database environment, and multiply the complexity found
there by the number of banks worldwide. Then, find a way to factor in
a many-to-many instead of a one-to-few achitecture.

And that rule of thumb completely ignores the fact that if a
transaction is fouled up anywhere along the line, one finds extensive
legal liability involved instead of a 'mere' corrupt table in a database.

-j

>jim

From: jamiel@sybase.com (Jamie Lawrence)

   And that rule of thumb completely ignores the fact that if a
   transaction is fouled up anywhere along the line, one finds extensive
   legal liability involved instead of a 'mere' corrupt table in a database.

When the algorithms include "Call legal dept. and sue", the ability of
most programmers to design systems goes out the window.

Jamie's estimate of the magnitude of the problem is probably
overstating the case, but not much.

Eric