Re: Passing XML back and forth with RPG and .NET

I completely agree with Charles...

My post was based on the idea that you've already decided to use XML by design, and that the decision to use XML is already set in stone. In that case, I think HTTP POST is the best way to handle passing the XML.

On the other hand, if the data format is still open for discussion, I'd say XML is overkill for most in-house projects, and indeed many projects that aren't in house. If you control both sides of the connection, I'd think long and hard before implementing XML. It's usually overkill.

Regular parameters on a stored procedure, UDF or UDTF call are much easier to code and much more efficient.

Charles Wilt wrote:

I second Scott's idea.

The other alternative would be to not use XML. Instead, use stored
procedures with regular parameters. Biggest downside to that is
there's no good way to pass for instance an array of detail records.

XML is nice for exchanging data outside your company, or at least with
applications outside your control. But if you control both sides, XML
adds some overhead that's usually not needed. However, since you're
dealing with two platforms and two languages it may be worthwhile.