>I have no idea. In my opinion, CFHTTP has been next to useless for quite >some time - it has many, many flaws. Oddly enough, MM solicited the opinions >of a bunch of CF developers (myself included) about what we'd like CFHTTP to >be able to do. Then, apparently, they disregarded all that stuff. Given MM's >track record with CFHTTP, I wouldn't expect anything to change very soon >with it.
I must confess that on this issue I find it rather difficult understand why there are ANY bugs at all after... what is it? Five years? Granted, they've changed from C++ to java recently but still... even so the languages aren't SO different that you'd throw away everything you would have learned. (In fact, they're similiar enough that a lot of the time it's hard to tell if you're looking at C++ or Java just at first glance.) I have a hard time understanding why it'd take more than a week or so to completely fix EVERYTHING that people have complained about over the years for CHTTP. You would think that in five years someone involved in the project would have actually read the RFC's involving HTTP1.0/1.1. :-) Anyway... it's all a mystery to me. (Not that I've used CFHTTP in years for the obvious reason.) >Fortunately, it doesn't matter all that much, as there are many alternatives >that you can use to accomplish the same thing. In CF MX, I've been testing >the Jakarta io JSP tag library, which seems to do most of the things I want >to be able to do with an HTTP client: >http://jakarta.apache.org/taglibs/ Nice. I *almost* don't look down on Java as a play-toy anymore. /-) --min ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
