XOM API for Processing XML with Java

["Jim Stuttard" <jim.stuttard AT btinternet.com>]

On Tue, 31 May 2005 09:21:58 -0400, John Cowan <jcowan AT reutershealth.com>  
wrote:

> produce two implementations at the same
> time.  This trick was used when developing the IBM 360 architecture,
> which was designed to be executable on a whole variety of systems with
> different price-performance.  The IETF's requirement for two independent
> interoperating implementations of any protocol to be standardized is
> probably related.
In couldn't agree more. If you don't try reversing any values in your  
first cut design then you haven't explored the problem. The permutations  
of interfaces and implementations are too complex to keep in your head at  
once so you might as well notate them as candidate implementation classes  
while your thinking about final designs. Two implementations also provide  
validation of algorithms and implementations and one can be seen as a test  
for the other. I've always been criticised for doing this as a waste of  
time but it hasn't stopped me since my C days.

So thanks for the IBM360 ref.

From now on I think I'll call this Xtreme Redundancy.

Cheers

Jim



--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/