I'll give this a go tonight. Thanks. On Tue, Nov 4, 2008 at 12:02 PM, Sheryl Barrow <[EMAIL PROTECTED]> wrote:
> > > On Tue, Nov 4, 2008 at 11:09 AM, Frederick Cheung < > [EMAIL PROTECTED]> wrote: > >> >> >> > Or am I going down the wrong path here? I don't actually need to >> > view the xml at any point - I'm actually going to pull it out of the >> > database at a later point and send it up to a web service. Or I >> > guess I could send it as it's generated, I just want to save it to >> > pull it later if need be. >> > > We do this very same thing. It may or may not be the best solution, but we > store the xml in a temp file on the server, and then have the path listed in > our MySQL database as text. We just read the whole thing and pass to the web > service when we're ready to move on. > > Our process goes like this: > > 1) Customer creates a cart and checks out. > 2) Call web services to generate the completed order xml. > 3) Save order xml into temp text file and put the path into the db. > 4) Display confirmation page with totals/taxes (generated from web > service). > 5) If confirmed, read order xml and call save method in web service. > > It's simple and doesn't require a whole bunch of coding. It also gives you > a nice history to look at if there are any problems with the xml. > > We remove the xml temp file once the order has been completed so it doesn't > eat all of our server space. > > Hope this helps! > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
