On 18/03/2009, at 11:35 PM, David FOXWELL wrote:
I would like your opinions on this subject. Am I wrong to say that  
the RPG program should do as much of the processing as possible?
Ask yourself this: If you were using RPG and display files would you  
do the editing of dates or numeric values in the RPG or in the DDS?  
It's the same here. Separation of duties is always a good thing--let  
the presentation manager handle presenting the data according to how  
the user wants to see it. This is really just another form of MVC. Who  
is responsible for editing data? The Model, the View, or the Controller?
The XML is not destined for use anywhere else but our own shop. We  
are fundamentally an RPG shop with as of yet limited XSL ressources  
( 1 expert and ...me!) . And then why use XSL when you can choose  
RPG for the job? Also, there's the performance question : I cannot  
believe that XSL would be anything other than sluggish by comparison  
to well - written RPG. On my PC, I've measured up to 7 seconds to  
transform an XML file and so generate one letter.
XSLT does seem slow. I've not bothered determining why. Some of it  
seems to be poor coding of the transform itself but much of it seems  
to be in the XSLT engine. XSLT seems to be CPU bound rather than main  
storage bound. Solution is to get a faster PC.
Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         OS/400, i5/OS Technical Specialists
   
http://www.flybynight.com.au/
   Phone: +61 2 6657 8251   Mobile: +61 0411 091 400        /"\
   Fax:   +61 2 6657 8251                                   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------
 
As an Amazon Associate we earn from qualifying purchases.
	
 
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.