RE: XML

I believe that for now I will give it a run on the client side and see how 
things work from there. The nice thing about that is it will take no time 
in .NET to write some code to create the XML. If I find that it is 
unacceptable, I have only wasted a few minutes of coding versus what it 
might take on the 400 side.

Thanks for the input everyone!!

    Dave Reiher
    System Analyst
    Prairie Farms Dairy - Corporate
    dreiher@xxxxxxxxxxxxxxxx



"albartell" <albartell@xxxxxxxxx> 
Sent by: web400-bounces@xxxxxxxxxxxx
11/11/2005 10:33 AM
Please respond to
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>


To
"'Web Enabling the AS400 / iSeries'" <web400@xxxxxxxxxxxx>
cc

Subject
RE: [WEB400] XML






I think XML is great for many things, the bad part is that it is being
implemented faster than network pipes and processors can handle it at 
speeds
that aren't noticeable.  I guess we will just have to live that for awhile
until connections get faster and machines get better processors.

>but if you move the creation to the iSeries now it's your problem.
Yep, that is the challenge with doing web services with RPG. When you 
don't
have to go through all of the different things relating to web services
(SOAP processing, schema validation, etc) then web services are actually
quite fast. But alas, with complexity on the .NET/Java end there are a lot
of features to be gained.


Aaron Bartell


-----Original Message-----
From: web400-bounces+albartell=gmail.com@xxxxxxxxxxxx
[mailto:web400-bounces+albartell=gmail.com@xxxxxxxxxxxx] On Behalf Of 
Walden
H. Leverich
Sent: Friday, November 11, 2005 8:50 AM
To: Web Enabling the AS400 / iSeries
Subject: RE: [WEB400] XML

Aaron,

>Note that adding XML as a db communication layer for a blackbox
application
>is asking for some real overhead issues. 

I don't want to put words in David's mouth, but since I've done something
similar I think I know what he's doing. It's not so much that XML is the
data transport layer as it's the data storage layer on the offline
application. 

Datasets have this marvelous ability to serialize themselves to/from and 
XML
stream. And since datasets can have multiple tables and even relationships
between the tables you can actually use the dataset as a mini-database. 
When
you're online load up the dataset from the iSeries and serialize it do a
local file. When offline simply serialize it in from the local file --
instant offline data access. 

My biggest concern with using anything other that the Dataset to serialize
out the XML in the first place is that you've got to get it right. Simple
XML is, um, simple, but throw in several tables, and the relations between
them and suddenly that XML gets rather ugly. It's not that it can't be 
done
from RPG -- heck XML is just text -- but if you continue to use .NET to
create the XML you're completely isolated from that ugliness, but if you
move the creation to the iSeries now it's your problem.

-Walden


------------
Walden H Leverich III
Tech Software
(516) 627-3800 x11
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)

--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post 
a
message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change 
list
options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/web400.