Re: sparse arrays - too complex?

> say "SOAP interopability is not safe - use another protocol."

That's ridiculous.  Write real-world code.  If you define services that
take arrays, nobody sane is going to send you a sparse array that
happens to have no holes.  If they do, Fault back.

Don't cut off the ENTIRE world because SOMEONE might squeeze through a
loophole.  It's generally not possible to use a human language to write
a document that has no ambiguity in it.

Applications that can benefit from spare arrays can benefit big-time;
it's nice to have a standard way of handling them.  And it's nice to
have a way to handle legacy RPC systems (DCE and therefore COM/DCOM)
that provided them, too.
	/r$
-- 
Zolera Systems, Securing web services (XML, SOAP, Signatures,
Encryption)
http://www.zolera.com