|
> --- Steve Richter wrote: > Jobs running in the interactive system are the heart > of the system. Interactive code has to be able to > spawn processes that run on the PC as well as the > server. Consider that iSeries Web applications may NOT run in the QINTER subsystem, but they ARE interactive. A Web page may contain say 3-5 inline frames, where each frame might have events associated with it, even timer events that evoke new server requests and target any frame in the browser window. In a "chat" application for example, the user may be keying a response in one frame while message content is being refreshed in another frame, concurrently. An iSeries Web application may be responding to client events that the user may not even know are being generated by the browser, as well concurrently responding to server events that the browser might be unaware of. Web applications can be HIGHLY interactive. Some of us may be so used to a typical 5250 model that we don't think outside the box. Then when Microsoft comes along with a proposal for a rich event driven user interface, we may think we have to jump on the band wagon to gain those kinds of results. Nothing could be further from the truth. Nathan M. Andelin __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com
As an Amazon Associate we earn from qualifying purchases.
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.