[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: XML-SAX opcodes vs. WSDL2RPG



What is there about XML-INTO that makes you omit it from the list?

I suspect that the tight integration of Expat into HTTPAPI might render it a little faster and depending on the complexity of the XML may make the programming a little simpler. But I have to believe that unless there is something really strange about your XML (and/or you are not yet at V6) that the best answer may well be "none of the above" - i.e. XML-INTO will be the simplest.

 
On 2012-07-10, at 12:48 PM, Carter Engelhart wrote:

>   We are at a decision point between using XML-SAX opcodes vs. WSDL2RPG
>   We have been unable to locate any credible reviews on which one is
>   better to use.
>   In our case we will be sending out a simple request from our iSeries
>   system via you httpapi product to an IBM P-Series server within our
>   fire wall to IBM's Intiate product and taking in an XML response that
>   we will need to break apart push to a DDS defined Physical File.
>   Our considerations for the decision are:
>   * Will it make the process easy to code>
>   * Will it make the process easy to debug?
>   * Is the product proven/reliable?
>   * Is the product supported by IBM?
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.  To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------

Jon Paris

www.partner400.com
www.SystemiDeveloper.com




-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------