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

Thanks Scott, I'll delve into this deeper. I had thought of that but was
hoping to avoid that extra layer of difficulty. It looks like it would make
more sense to pursue that route vs. the other methods.

--
Mike Wills
http://mikewills.info
P: (507) 933-0880 | Skype: koldark


On Tue, Dec 1, 2009 at 12:56 PM, Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>wrote:

I would have the .NET invoke the RPG via HTTP and send the XML document
as POST data. Have the RPG return it's response the same way. No need
to put the XML data into a file at all.

In the event that you need to use XML-INTO or XML-SAX and are on V5R4 or
earlier (and therefore have to cope with the annoying 64k limit) I would
have the RPG temporarily throw the XML data into a user space, and parse
the user space. (Make sure you set unused data in the user space to
blanks.)

User spaces can be parsed by XML-INTO/XML-SAX via the doc=file and
giving a filename of /QSYS.LIB/QTEMP.LIB/WHATEVER.USRSPC -- and user
spaces are very fast.


Mike wrote:

I am at a loss here of a best-practice to pass XML back and forth with

RPG

and C#.NET. Originally, I was going to use a temp physical file in QTEMP,
but it seems to be that there should be a better way. The temp file has

one

line of the document in one record of the file. To me this seems to add a
lot of extra work that really shouldn't be needed. I am looking for a
two-way communication.

One thought is to pass a 32000 char parameter back and forth, but is that
really a good idea? What happens if the document happens to be bigger

than

that? I don't think I would hit that limit so maybe I would be fine?

What about creating a temp IFS file? That seems like more work than is
needed as well.

What are your thoughts?

Obviously, both the RPG and C# programs will be reading and processing

the

XML document.

I have x-post this on systemidotnet as well to get both sides. I hope

David

doesn't mind