It is all to a web address, http post required to do the data transfer. And finally, each of the steps is to a separate server (or web address) following through so we are not worried with consecutive requests and the line being open. Okay, maybe we were overthinking ourselves on this one? Thanks for the pointers! Now, when we get that gif image back in our final request....how do we deal with extracting that? Hahah We'll figure that out I think. Thanks again, Jon.
Regards, Eric J Hoffman DataStream Connexion www.datastreamconnexion.com Delivering Creative Data Solutions -----Original Message----- From: Jon Hall [mailto:[EMAIL PROTECTED]] Sent: Friday, July 26, 2002 5:11 PM To: CF-Talk Subject: Re: XML Questions (newbie) Usually the receiving end is very specific on how they want the xml given to them. If you are using cfhttp there are two ways, either do a http get, which means the xml packet will be sent as a url variable, or an http post, which means the xml packet will be sent as a form variable. You may want to read over my post titled, "Re: It's official: CFMX is 10% faster than CF5" if you plan on using cfhttp to send xml. There are issues that may rule out cfhttp. If you can do an http get, life is wonderful, otherwise, you are probably going to need an external component to send the xml, like Lewis Sellers tcpclient (unless you need ssl), or msxml, or depending on what they specify, any one of the other zillion ways to send information across the wire. Now that I think about it, the back and forth three times, is not a big deal, but it may rule out cfhttp, as it is serial only. Meaning it will not reuse the same connection to reply back to the server, on the second go around. It depends on how the other end wants it. Personally I use msxml for all my xml stuff from CF, Dave Watt's will tell you to try TCPClient, and the Lewis Sellers will pop in and say that ssl support is coming as soon as the government gets off it's butt... :) Checking the archives, once you get everything you need to down, the code for the different ways has been posted before. Of course both these ways presume you are on a Windows machine. That doesn't mean I won't post it again, just that you may glean more varied info from the archives :) -- Jon mailto:[EMAIL PROTECTED] Friday, July 26, 2002, 5:03:12 PM, you wrote: EH> We are on CF 5. EH> We know it's a valid XML file, so great, we use cfsavecontent dump EH> it to a xml variable. Now the receiving server we figured we would EH> send to via CFHTTP...and we will get a response code(s) in XML EH> format, yes, so that's where we are wondering how that handles...its EH> actually a wonderful back and forth 3 times before approval. Argh. EH> Thanks for helping clear up 67% of the battle...we have been on the EH> right track...so CFHTTP the file...your thoughts? EH> Thanks a million! EH> Regards, EH> Eric J Hoffman EH> DataStream Connexion EH> www.datastreamconnexion.com EH> Delivering Creative Data Solutions EH> -----Original Message----- EH> From: Jon Hall [mailto:[EMAIL PROTECTED]] EH> Sent: Friday, July 26, 2002 3:55 PM EH> To: CF-Talk EH> Subject: Re: XML Questions (newbie) EH> I'll assume that your xml code or packet is valid xml that the other EH> side can understand it. After that it is fairly simple to send it along. EH> You need to get the entire xml packet string into a variable. For EH> examples sake: <cfsavecontent var="xmlPacket"> <foo> EH> <cfoutput query="bars"> EH> <bar>#bars.picklejuice#</bar> EH> </cfoutput> EH> </foo> EH> </cfsavecontent> EH> So the xmlPacket variable now contains your xml. All you have to do is EH> send it somewhere. Note, the above xml is not valid...just an example. EH> Sending it to the right place is one thing, but has the other end EH> specified _how_ you are supposed to send it? You may simply be able to EH> use cfhttp, let me know, and I shall point in the right direction :). EH> Also the other side of this is that you will be getting back a response EH> xml packet from the other end I presume? That's is where you may want to EH> use SoXML, to get the packet into a CF native datatype (a structure). If EH> you are using MX, you can use it's built in XML functions for this. EH> There are some nice, a cheap Java based, xml parsers for CF as well. EH> FYI: SoXML is just a CF wrapper for MsXML, so it isn't going to work in EH> MX yet, and I don't believe it has the capability to uses msxml to EH> trasmit the packet. ______________________________________________________________________ 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/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
