Janus Web Legacy XML Support: Difference between revisions
m (Created page with "<var class="product">Janus Web Legacy XML Support</var> is a variant of <var class="product">Janus Web Legacy Support</var> that is intended to facilitate programmatic access to ...") |
mNo edit summary |
||
| Line 1: | Line 1: | ||
<var class="product">Janus Web Legacy XML Support</var> is a variant of <var class="product">Janus Web Legacy Support</var> that is intended to facilitate programmatic access to legacy 3270 applications. This is accomplished by converting 3270 screens into XML that contains the names and values of the screen fields, and accepting updates to these screens as XML that contains the names and updated values of the screen fields. Because screen field names are used for screen retrieval and update, programs that access 3270 screens via <var class="product">Janus Web Legacy XML Support</var> are not vulnerable to cosmetic changes to pages and so are much more robust than traditional [http://en.wikipedia.org/wiki/Data_scraping#Screen_scraping screen scraping] and [http://en.wikipedia.org/wiki/Web_scraping web scraping] applications. And, delivery of 3270 screens over an HTTP connections means that they can be access via any of a large number of HTTP APIs available in most modern programming environments. | <var class="product">Janus Web Legacy XML Support</var> is a variant of <var class="product">Janus Web Legacy Support</var> that is intended to facilitate programmatic access to legacy <var class="product">Model 204</var> 3270 applications. This is accomplished by converting 3270 screens into XML that contains the names and values of the screen fields, and accepting updates to these screens as XML that contains the names and updated values of the screen fields. Because screen field names are used for screen retrieval and update, programs that access 3270 screens via <var class="product">Janus Web Legacy XML Support</var> are not vulnerable to cosmetic changes to pages and so are much more robust (and easier to develop) than traditional [http://en.wikipedia.org/wiki/Data_scraping#Screen_scraping screen scraping] and [http://en.wikipedia.org/wiki/Web_scraping web scraping] applications. And, delivery of 3270 screens over an HTTP connections means that they can be access via any of a large number of HTTP APIs available in most modern programming environments. | ||
Revision as of 17:28, 10 November 2012
Janus Web Legacy XML Support is a variant of Janus Web Legacy Support that is intended to facilitate programmatic access to legacy Model 204 3270 applications. This is accomplished by converting 3270 screens into XML that contains the names and values of the screen fields, and accepting updates to these screens as XML that contains the names and updated values of the screen fields. Because screen field names are used for screen retrieval and update, programs that access 3270 screens via Janus Web Legacy XML Support are not vulnerable to cosmetic changes to pages and so are much more robust (and easier to develop) than traditional screen scraping and web scraping applications. And, delivery of 3270 screens over an HTTP connections means that they can be access via any of a large number of HTTP APIs available in most modern programming environments.