Re: IBM i "Open I/O" Architecture -- MIDRANGE-L

Subject: Re: IBM i "Open I/O" Architecture
From: Nathan Andelin <nandelin@xxxxxxxxx>
Date: Wed, 21 Oct 2009 10:10:05 -0700 (PDT)
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: IBM i "Open I/O" Architecture , Mike Cunningham

This mailing list archive is Copyright 1997-2024 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.