>The only good reason I can see for going with a two-loop solution is the >fact that we're fairly close to a final release right now and might want >to keep the code stable. On the other hand, if we're going to make a >semantic API change like this, it's probably better to do it now, before >2.0 final.
Personally, I feel it's too late in the release process to be moving all the redirect code around, however that does depend on how inelegant the other options are. If we don't move it until after the 2.0 release, we should add a note on any method that is likely to be affected by the change that the change will happen and so you shouldn't depend on this code being here. (Much like Sun's warning about serializing Swing objects). I'd also suggest that we make HttpClient more flexible so that Laura can use it directly since that would then discourage people from using the methods directly and changes like this will be much less of a concern in the future. Course, I don't have time to actually do any of this, so feel free to just ignore me. :) Adrian Sutton, Software Engineer Ephox Corporation www.ephox.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
