> ----------
> From: NAGEL Erlend[SMTP:[EMAIL PROTECTED]]
>
> It may be the context in which screen scraping was present (silver
> bullit there as well?). One place where "screen scraping" is a useful
> tool, is where you have an application that is critical to your
> business process and to which you need an updated electronic
> interface, but there is none, and you cannot change the
> application/have it changed. In this case, it is possible to build
> both webbased user interfaces and EDI-type machine interfaces, where
> the screen scraping technology makes the "legacy" application is
> encapsulated. Of course the key thing is that the application CANNOT
> be changed. Instead it should become just a component that you can
> replace when needed, with the same interfaces in place.
>
This is a perfectly legitimate reason to scrape a screen. Note the key
thing that you mention -- "the application CANNOT be changed." Just as you
don't change versions or add segments or spit into the wind, you don't
change applications willy-nilly.
The best way to ensure this, of course, is to control the source of both the
legacy app and the gui that is scraping the screen.
The worst way to ensure this is to scrape your trading partner's screen,
because you may never know when they change something.
=======================================================================
To signoff the EDI-L list, mailto:[EMAIL PROTECTED]
To subscribe, mailto:[EMAIL PROTECTED]
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
