<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/1.5.1.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Screen-Scraping with OPS</title>
	<link>http://www.orbeon.com/blog/2005/03/31/screen-scraping-with-ops/</link>
	<description>XForms Everywhere</description>
	<pubDate>Sat, 30 Aug 2008 00:13:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.1.3</generator>

	<item>
		<title>by: Hank Ratzesberger</title>
		<link>http://www.orbeon.com/blog/2005/03/31/screen-scraping-with-ops/#comment-167</link>
		<pubDate>Wed, 13 Apr 2005 04:43:07 +0000</pubDate>
		<guid>http://www.orbeon.com/blog/2005/03/31/screen-scraping-with-ops/#comment-167</guid>
					<description>Another article on Screen Scraping.  Not too clear from the text, but it sounds like the strategy is to create wsdl descriptions for things like CICS mainframe applications.  If there really is a way to to streamline that, it would be great.  The main point, is that scraping is an option where the the data and code are difficult to separate.

http://idevnews.com/PrintVersion.asp?ID=161</description>
		<content:encoded><![CDATA[	<p>Another article on Screen Scraping.  Not too clear from the text, but it sounds like the strategy is to create wsdl descriptions for things like CICS mainframe applications.  If there really is a way to to streamline that, it would be great.  The main point, is that scraping is an option where the the data and code are difficult to separate.</p>
	<p><a href='http://idevnews.com/PrintVersion.asp?ID=161' rel='nofollow'>http://idevnews.com/PrintVersion.asp?ID=161</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jay</title>
		<link>http://www.orbeon.com/blog/2005/03/31/screen-scraping-with-ops/#comment-163</link>
		<pubDate>Tue, 05 Apr 2005 11:13:51 +0000</pubDate>
		<guid>http://www.orbeon.com/blog/2005/03/31/screen-scraping-with-ops/#comment-163</guid>
					<description>Many years ago (6 to be precise), I used a specific language called &lt;a href=&quot;http://www.w3.org/TR/NOTE-widl-970922&quot;&gt;WIDL&lt;/a&gt; to do exactly this, but using search engines as targets to do meta-searching. Automating screen-scraping works fine, until the interface changes (for some odd reason, such as to avoid having &quot;screen-scraping&quot; applications interfacing :). A fine example of such an application is &lt;a href=&quot;http://jbidwatcher.sf.net&quot;&gt;JBidWatcher&lt;/a&gt;, which uses the same principle and must create a new version every so often, when eBay changes the layout of it's pages. If you can, you're better off creating a SOAP or REST interface to your legacy apps, than just to depend on HTML views of your data. Trust me, I've been there (and back ;).</description>
		<content:encoded><![CDATA[	<p>Many years ago (6 to be precise), I used a specific language called <a href="http://www.w3.org/TR/NOTE-widl-970922">WIDL</a> to do exactly this, but using search engines as targets to do meta-searching. Automating screen-scraping works fine, until the interface changes (for some odd reason, such as to avoid having &#8220;screen-scraping&#8221; applications interfacing :). A fine example of such an application is <a href="http://jbidwatcher.sf.net">JBidWatcher</a>, which uses the same principle and must create a new version every so often, when eBay changes the layout of it&#8217;s pages. If you can, you&#8217;re better off creating a SOAP or REST interface to your legacy apps, than just to depend on HTML views of your data. Trust me, I&#8217;ve been there (and back ;).
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Erik Bruchez</title>
		<link>http://www.orbeon.com/blog/2005/03/31/screen-scraping-with-ops/#comment-162</link>
		<pubDate>Mon, 04 Apr 2005 17:39:25 +0000</pubDate>
		<guid>http://www.orbeon.com/blog/2005/03/31/screen-scraping-with-ops/#comment-162</guid>
					<description>Thanks for the precision! It is a similar approach with HTML screen-scraping. You could build &quot;modern&quot; web services on top of legacy HTML-based applications. If you really need to interact with the application, you would need to be able to post forms as well.</description>
		<content:encoded><![CDATA[	<p>Thanks for the precision! It is a similar approach with HTML screen-scraping. You could build &#8220;modern&#8221; web services on top of legacy HTML-based applications. If you really need to interact with the application, you would need to be able to post forms as well.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Hank Ratzesberger</title>
		<link>http://www.orbeon.com/blog/2005/03/31/screen-scraping-with-ops/#comment-161</link>
		<pubDate>Mon, 04 Apr 2005 17:12:13 +0000</pubDate>
		<guid>http://www.orbeon.com/blog/2005/03/31/screen-scraping-with-ops/#comment-161</guid>
					<description>Erik, you're too modern!  Screen Scraping is actually an acceptable way to create an interface to a legacy app.  I can't find the  information on the IBM team working on this, but an example of pushing AS400 green screens to the web via scraping:
http://www.jacada.com/Products/Legacy_Extension.htm .  It was a way of putting an interface on a legacy app while you re-architected it, but I'm not sure that once companies created a thin client layer, they had a lot of incentive to rewrite the application in, say Websphere.</description>
		<content:encoded><![CDATA[	<p>Erik, you&#8217;re too modern!  Screen Scraping is actually an acceptable way to create an interface to a legacy app.  I can&#8217;t find the  information on the IBM team working on this, but an example of pushing AS400 green screens to the web via scraping:<br />
<a href='http://www.jacada.com/Products/Legacy_Extension.htm' rel='nofollow'>http://www.jacada.com/Products/Legacy_Extension.htm</a> .  It was a way of putting an interface on a legacy app while you re-architected it, but I&#8217;m not sure that once companies created a thin client layer, they had a lot of incentive to rewrite the application in, say Websphere.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
