Comments on: My ColdFusion MX 7 Wishlist: How Did Macromedia Do?

By: wahyu

wahyu — Wed, 29 Apr 2009 09:35:45 +0000

I got a connection failure when using cfhttp. I have provided the values for the following attributes: url, port, method, proxyserver, proxyport, proxyuser, proxypassword, username, password, and resolveurl=yes. But still got the Connection Failure message. Is there a solution for this error?

By: Brandon Harper

Brandon Harper — Fri, 08 Jul 2005 19:32:35 +0000

Yeah, it’s been quite awhile since I played with the particular script which was running cfhttp. I honestly can’t remember if it was 6.0 or 6.1 at this point.

Basically the script looped through many, many URL’s and seemed like it took forever. Someone else at the time had CF 5 on their box at work and the speed difference to run the same script was simply dramatic– 6.X would take almost a minute to run, while 5 would process it in less than 10 seconds. Probably a rare test case where you would need to use that functionality anyway, but the difference in performance between the two was pretty astounding. It certainly could of been that cfhttp on 6.X was doing DNS lookups each time and maybe 5 only did it once (they were all calls to the same domain)… no idea really.

By: Tom Jordahl

Tom Jordahl — Fri, 08 Jul 2005 14:34:06 +0000

Re: cfhttp. The tag was rewritten for ColdFusion MX 6.1 (Redsky) and does not have any (known) performance issues. We use a different HTTP client library than the JDK URLConnection class that was used in 6.0.

By: Brandon Harper

Brandon Harper — Wed, 25 May 2005 15:47:37 +0000

Thanks Ray. I haven’t touched a webservice since before 6.1, but that’s very useful information to know.

By: Raymond Camden

Raymond Camden — Wed, 25 May 2005 14:01:47 +0000

Actually there was _lot_ done with WS. Along with being able to inspect the SOAP request/response, you can also modify them now. You can call different service ports on a WS (which apparently is an extremely rare use-case, but used in MS MapPoint). You can also check to see if the current request is a SOAP request. This would let you check in a CFC if you are being called via FR or WS.

There is more too – from the release notes:

The cfinvokeargument tag has a new omit attribute that allows you to omit arguments to a web service that you invoke.

New cfcomponent attributes enable ColdFusion MX to publish document-literal style web services.

* style=”document” : switches the emitted WSDL to document/literal style.
* hint is now used as the document element of the service in WSDL.
* displayName is now used as the name of the element in WSDL.
* servicePortName is used as the name of the element in the service.
* portTypeName is used as the name of the element in WSDL.
* bindingName is used as the name of the element in WSDL.
* namespace is used as the default namespace of the service.
* wsdlFile=”" – Use this file as the WSDL instead of generating
WSDL on the fly.