-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> 7. Fix CFHTTP!  Please!  In the current implementation so 
> much is broken it's not even funny!

Not that a few other folks haven't mentioned this, but.....

ME TOO!!!

To add some more specific requests:  

* 4.5.1 broke templates which retrieved MIME types other than
"text/html" (and a few others).  CFHTTP should NOT assume that just
because something isn't in its list of text types that it isn't
indeed text.  This issue might very well be fixed as part of
implementing binary stuff support, but it DOES need to be fixed.  At
the very least, let me configure what MIME types are text myself!

* I'd like to have full control of both the headers SENT and RECEIVED
in the CFHTTP request.  

* Some intelligent parsing of multipart/MIME encoded responses would
be REALLY nice.  I had to write my own CFHTTP hack as a CFX tag to
access UPS's online shipping & other functions, but most of that work
could easily (and sensibly) be included in CFHTTP.

* I definitely want to see the entirety of CF's functionality be
accessible from CFSCRIPT blocks.  They're SO much nicer to write for
us procedural language types (at least for certain applications), and
rumor has it they're faster to parse.


Just my $.02...

Best regards,
Zac Bedell

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>
Comment: Please use PGP!!!

iQA/AwUBOaq1QwraVoMWBwRBEQIEbQCg6BM+2iyHpW2MNixZrtxJCEFXt10AoLjk
QyZNV/sinLxbPUhCl9X4TIwr
=0lT/
-----END PGP SIGNATURE-----
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to