I don't think we should do this. I'd really rather get 1.0 out with this limitation noted and then make this an extremely high priority for 1.1. Just to be clear I do realize this is a potential issue for many people, but fixing it would delay a release by at least a month or more. We've had 1.0 on the verge of release for almost five months, and right now it's stalling the project overall. We have enough other issues that we really need to just ship 1.0, clear the blockage and get back to making rapid progress.
I agree. Let's ship a 1.0 that does some XML encodings in a more robust fashion, rather than potentially introduce instability by attempting to support all XML encodings.
BTW, I'm going to checkin a minor change to SystemCollection that stores the SysConfig collection as a standard compressed collection rather than an uncached, uncompressed Collection. The latter was required when the SysConfig collection pointed to a directory, but it's no longer necessary. This change will require a complete db rebuild though.
Name for RC2 will be Pepper. If it's 1.0, then it's Birthday
-- Tom Bradford - http://www.tbradford.org Architect - XQRL (XQuery Engine) - http://www.xqrl.com Apache Xindice (Native XML Database) - http://xml.apache.org Project Labrador (Web Services Framework) - http://notdotnet.org
