>> You dont need AJAX to publish the content. 

yes, I wasn't saying that. It was more about how to get it to them and you're 
right, they probably won't be using AJAX (I'm under the understanding that 
because of security JS can't access across domains, yes?)

>> just cfoutput the xml

yep. same way of pushing xml to AJAX. bringing up the XML in the browser isn't 
a bad way of checking the xml output either

just a reminder: when you're pushing XML like this, whitespace around the 
document is a killer so don't forget the 
 
<cfsetting enablecfoutputonly="Yes">

or similar

but yeah, Pat's suggestion is probably the simplist way to go.

Brian, any idea how they're going to consume the XML? that'll be the decider...

cheers
barry.b

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Pat
> Branley
> Sent: Friday, 20 May 2005 3:03 PM
> To: CFAussie Mailing List
> Subject: [cfaussie] Re: Generating XML files
> 
> 
> You dont need AJAX to publish the content. They possibly 
> could use AJAX 
> to consume it. But i doubt they would if its for getting data into a 
> back-end system.
> 
> just cfoutput the xml and get them to make a <cfhttp call (if 
> they are 
> running cold fusion, other langauges have similar ways of getting 
> content from a URL)
> 
> You can secure it more by making the url HTTPS and doing some 
> IP address 
> checks on the remote server requesting the docs, even put web server 
> authentication on the page if you feel you need it.
> 
> This is how alot of people are doing XML over the web these days, 
> particularly in PHP community. From what i understand its 
> because they 
> dont have the coolness of cold fusion's access="remote" way of 
> publishing webservices.
> 
> Web services are cool, but if the interaction is just one 
> way. XML over 
> HTTP is the easiest way...
> 
> my 2c
> 
> pat
> 
> Barry Beattie wrote:
> > Brian, the key is how to get the XML to them (if it's XML 
> they're keen 
> > to consume)
> >  
> > sure you can use CFXML to build the document, but for them 
> to use it, 
> > what would they do?
> >  
> > if it was AJAX stuff (and they were on the same domain) 
> you'd just give 
> > them a URL (with query params for the order number) and all 
> you'd have 
> > to do is <cfoutput> the xml built from the CFXML (there's a 
> touch more 
> > to it than that but it's not hard). At a guess this is 
> probably not what 
> > you want to do but I'll soapbox anyway...
> >  
> > but chances are they're on a seperate domain so it sounds like a 
> > webservice might be the go. That way all they have to do is 
> call the 
> > correct CFC (it'd be a facade to the real CFC, yes?). 
> Again, build your 
> > doc with CFXML (if that's the way you're happy with), but the 
> > return/output would be via the CFC (ie: access="remote").
> >  
> > either that or it's "screen scraping" with cfhttp or file 
> transfer to 
> > their system with cfftp, neither of them are nice...
> >  
> >  
> > just some thoughts
> > barry.b
> >  
> >  
> >  
> >  
> >  
> >  
> >  
> >  
> >  
> >  
> > 
> >     -----Original Message-----
> >     *From:* [EMAIL PROTECTED]
> >     [mailto:[EMAIL PROTECTED] Behalf Of
> >     *KNOTT, Brian
> >     *Sent:* Friday, 20 May 2005 11:34 AM
> >     *To:* CFAussie Mailing List
> >     *Subject:* [cfaussie] Generating XML files
> > 
> >     What's the preferred method these days of generating XML files.
> > 
> >      
> > 
> >     I have an order system and a third party wants to get 
> an XML feed of
> >     orders.  Should I be using CFXML or a web service.
> > 
> >      
> > 
> >     Brian Knott
> > 
> >     
> --------------------------------------------------------------
> ---------------------
> > 
> > 
> >     This e-mail is sent by Suncorp-Metway Limited ABN 66 
> 010 831 722 or
> >     one of its related entities "Suncorp".
> > 
> >     Suncorp may be contacted at Level 18, 36 Wickham 
> Terrace, Brisbane
> >     or on 13 11 55 or at suncorp.com.au.
> > 
> >     The content of this e-mail is the view of the sender or stated
> >     author and does not necessarily reflect the view of Suncorp. The
> >     content, including attachments, is a confidential communication
> >     between Suncorp and the intended recipient. If you are not the
> >     intended recipient, any use, interference with, disclosure or
> >     copying of this e-mail, including attachments, is 
> unauthorised and
> >     expressly prohibited. If you have received this e-mail in error
> >     please contact the sender immediately and delete the 
> e-mail and any
> >     attachments from your system.
> > 
> >     If this e-mail constitutes a commercial message of a 
> type that you
> >     no longer wish to receive please reply to this e-mail by typing
> >     Unsubscribe in the subject line.
> > 
> >     ---
> >     You are currently subscribed to cfaussie as: 
> [EMAIL PROTECTED]
> >     To unsubscribe send a blank email to 
> [EMAIL PROTECTED] Aussie
> >     Macromedia Developers: http://lists.daemon.com.au/ 
> 
> ---
> You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
> To unsubscribe send a blank email to 
> [EMAIL PROTECTED]
> Aussie Macromedia Developers: http://lists.daemon.com.au/
> 

---
You are currently subscribed to cfaussie as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/

Reply via email to