On Thu, Aug 11, 2016 at 6:14 PM, Roy T. Fielding <field...@gbiv.com> wrote:
> I have no idea why there is any need to discuss EBCDIC here, since HTTP > itself > is never EBCDIC. We should not be transforming any input to EBCDIC until > after the request has been parsed. > Just as a point of information, that isn't how this works, it isn't how any of this works. All of the raw text off the wire has been turned into platform-specific encoding on EBCDIC architectures after a simple bucket-fetch readline. There is no realistic way to code ASCII logic on a non-ASCII C compiler, so I agree with the design model. If you would like to refactor that and deal with the consequences, be our guest. In any case, if you have a working parser implementation, I will be happy to > review it regardless of my preferences. If it is better than what we > have, then > it will still get my +1 for trunk regardless of longer term plans. > I think we are on the same page, I welcome your's and other's improvements and enhancements, and we should ship a release. These ideas aren't irreconcilable. Thanks for your support, I expect we will all agree, in some round about way, a few months from now. Cheers, Bill
