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

.Net has no issues accessing an IFS folder. As far as it is concerned it is
just another text file. I have moved data back and forth many times using a
temporary IFS file.

On Tue, Dec 1, 2009 at 11:45 AM, Mike Wills <koldark@xxxxxxxxx> wrote:

One problem that I should have mentioned, .NET can only call stored
procedures or use the database. It can't access (directly) the IFS.
I'll look into Scott's EXPAT a bit closer though.

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

On Dec 1, 2009, at 12:29 PM, Alan Campin wrote:

Use the temp IFS. Scott's EXPAT parser will read directly from an
IFS table
and they are very fast. Writing to a physical file is slow. There
should be
nothing to writing to the IFS. I have a service program that wrappers
everything that I use. The parsing back would be handled by EXPAT.

You could also pass a 64k varchar but like you said it might be too
big.
V6R1 has much bigger limits.

On Tue, Dec 1, 2009 at 10:59 AM, Mike <koldark@xxxxxxxxx> 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.

--
Mike Wills
http://mikewills.info
P: (507) 933-0880 | Skype: koldark
--
This is the RPG programming on the IBM i / System i (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

--
This is the RPG programming on the IBM i / System i (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing

list

To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.