×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
From: Mike Cunningham
Instead of having the Open I/O code in the RPG application that code
would all be external to the RPG application and inside the external
object.
I kind of get your drift. After all, the goal is to streamline interfaces to make programming easier and more productive. CRTDSPF for example, creates an object that can be easily reference by IBM utility code, to streamline the WORKSTN interface.
With respect to Open I/O, maybe this is the part where vendors step in and create various objects from some sort of DDS equivalent, which can be easily used by their utility code, which may be implemented in generic Open I/O handlers.
-Nathan.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: Wednesday, October 21, 2009 1:10 PM
To: Midrange Systems Technical Discussion
Subject: Re: IBM i "Open I/O" Architecture
From: Mike Cunningham
Have a object type of HTML ... Then throw in an object type of IPHONE,
PDA, ANDROID, ORACLE, MYSQL, MSSQL....
Object type? Do you mean device type? Extend beyond the traditional PRINTER, DISK, WORKSTN, and SPECIAL device types? No matter how long the list of devices the interface may support, there will always be devices that are not supported. That idea may be the type of over-engineering that Jon expressed fear of. Bummer, they left out Adobe FLEX, Microsoft Silverlight, DOJO Clients, and barcode readers as device types.
That's one of the reasons that the idea of Open I/O handlers is more attractive - the interface would not be closed to any particular client device.
-Nathan.
midrange.com
