<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: The reliability of web services</title>
	<link>http://www.perrygeo.net/wordpress/?p=57</link>
	<description>Matt Perry's random adventures with geospatial technology and other tangentially related topics</description>
	<pubDate>Thu, 09 Sep 2010 15:35:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: estetik</title>
		<link>http://www.perrygeo.net/wordpress/?p=57#comment-37471</link>
		<dc:creator>estetik</dc:creator>
		<pubDate>Thu, 06 Dec 2007 19:56:02 +0000</pubDate>
		<guid>http://www.perrygeo.net/wordpress/?p=57#comment-37471</guid>
		<description>Very good article. I don't believe web services give right information on their frontpages especially about uptime percentages.</description>
		<content:encoded><![CDATA[<p>Very good article. I don&#8217;t believe web services give right information on their frontpages especially about uptime percentages.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Smith</title>
		<link>http://www.perrygeo.net/wordpress/?p=57#comment-2649</link>
		<dc:creator>Dave Smith</dc:creator>
		<pubDate>Sun, 01 Oct 2006 15:27:28 +0000</pubDate>
		<guid>http://www.perrygeo.net/wordpress/?p=57#comment-2649</guid>
		<description>In publishing a service that will be connected to, lights-out, by the public and stakeholders one might not even be aware of, the hope is that the owner of the service considers these aspects in advance.  This goes toward the overall strategy and service level agreement (SLA).  What is the backup and replication strategy?  How reliable is the service expected to be in terms of throughput and uptime?  How about data latency - is it going to be updated on a reliable basis?  Data accuracy?  Is the service something that has solid and ongoing funding as part of a bigger program, is it just a proof-of-concept or pilot, or are there other contingencies to consider in terms of longterm viability?  These things may have some impact on whether others will even consider the published service worthwhile...  Some plan, or better yet, a published metadata describing these aspects should be on the radar of any service provider.</description>
		<content:encoded><![CDATA[<p>In publishing a service that will be connected to, lights-out, by the public and stakeholders one might not even be aware of, the hope is that the owner of the service considers these aspects in advance.  This goes toward the overall strategy and service level agreement (SLA).  What is the backup and replication strategy?  How reliable is the service expected to be in terms of throughput and uptime?  How about data latency - is it going to be updated on a reliable basis?  Data accuracy?  Is the service something that has solid and ongoing funding as part of a bigger program, is it just a proof-of-concept or pilot, or are there other contingencies to consider in terms of longterm viability?  These things may have some impact on whether others will even consider the published service worthwhile&#8230;  Some plan, or better yet, a published metadata describing these aspects should be on the radar of any service provider.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raj</title>
		<link>http://www.perrygeo.net/wordpress/?p=57#comment-1094</link>
		<dc:creator>Raj</dc:creator>
		<pubDate>Tue, 01 Aug 2006 18:28:45 +0000</pubDate>
		<guid>http://www.perrygeo.net/wordpress/?p=57#comment-1094</guid>
		<description>Great discussion topic. I've been thinking about this a lot lately, and so have many others here: http://wiki.osgeo.org/index.php/WMS_Tile_Caching. The problem with WMS is that there's a cost/benefit mismatch between what you want--a pretty map--and what it takes to deliver that to you--lots of computation to rasterize vector data. That's why OGC and others are working on a tiling scheme for WMS so that you can pre-generate your maps and just serve out files, like all the big street mapping sites do now anyway.</description>
		<content:encoded><![CDATA[<p>Great discussion topic. I&#8217;ve been thinking about this a lot lately, and so have many others here: <a href="http://wiki.osgeo.org/index.php/WMS_Tile_Caching." rel="nofollow">http://wiki.osgeo.org/index.php/WMS_Tile_Caching.</a> The problem with WMS is that there&#8217;s a cost/benefit mismatch between what you want&#8211;a pretty map&#8211;and what it takes to deliver that to you&#8211;lots of computation to rasterize vector data. That&#8217;s why OGC and others are working on a tiling scheme for WMS so that you can pre-generate your maps and just serve out files, like all the big street mapping sites do now anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.perrygeo.net/wordpress/?p=57#comment-1070</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Sun, 30 Jul 2006 21:33:33 +0000</pubDate>
		<guid>http://www.perrygeo.net/wordpress/?p=57#comment-1070</guid>
		<description>Interesting experiment, Matt.  I am working on a Colorado WMS/WFS project at the moment and  
reliability is one of the issues that I am curious about.  Do you think it has to do with the 
particular server hardware or an issue specific to WMS services?

Very interesting.

Chris</description>
		<content:encoded><![CDATA[<p>Interesting experiment, Matt.  I am working on a Colorado WMS/WFS project at the moment and<br />
reliability is one of the issues that I am curious about.  Do you think it has to do with the<br />
particular server hardware or an issue specific to WMS services?</p>
<p>Very interesting.</p>
<p>Chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy</title>
		<link>http://www.perrygeo.net/wordpress/?p=57#comment-958</link>
		<dc:creator>Jeremy</dc:creator>
		<pubDate>Tue, 25 Jul 2006 14:13:23 +0000</pubDate>
		<guid>http://www.perrygeo.net/wordpress/?p=57#comment-958</guid>
		<description>Good post Matt.  We have a project where we integrate around 30 map services in a targeted portal.  We use everything from large National services (seamless, Geography Network, etc) to smaller scale services specific to the project (project partners).  The major organizations are quite stable actually.  The services that are run out of University's with mostly graduate student help are the ones that go down the most.  Check it out &lt;a href="http://drysdale.kgs.ku.edu/natcarb/midflash/natcarb_new.html" rel="nofollow"&gt;here&lt;/a&gt; if you are interested.  The fun thing about the project is that we have been doing this for about two years and we have statistics/uptime for that entire time period.

Jeremy</description>
		<content:encoded><![CDATA[<p>Good post Matt.  We have a project where we integrate around 30 map services in a targeted portal.  We use everything from large National services (seamless, Geography Network, etc) to smaller scale services specific to the project (project partners).  The major organizations are quite stable actually.  The services that are run out of University&#8217;s with mostly graduate student help are the ones that go down the most.  Check it out <a href="http://drysdale.kgs.ku.edu/natcarb/midflash/natcarb_new.html" rel="nofollow">here</a> if you are interested.  The fun thing about the project is that we have been doing this for about two years and we have statistics/uptime for that entire time period.</p>
<p>Jeremy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://www.perrygeo.net/wordpress/?p=57#comment-953</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Tue, 25 Jul 2006 13:16:50 +0000</pubDate>
		<guid>http://www.perrygeo.net/wordpress/?p=57#comment-953</guid>
		<description>Not to be an ESRI "fan boy" (as Sean Gilles would call me), but this is one reason that I really like the new geodatabase replication that's coming with ArcGIS 9.2 - you can cascade data between organizations, bi-directionally, at the database level. Since you have all the data locally, and it's kept in synch with the original source, your application is not dependant on the uptime of the remote service. Of course this functionality is not "free", but it's better than relying on inconsistent services for mission criticla datasets

Here's a link to the web help about &lt;a href="http://webhelp.esri.com/arcgisdesktop/9.2/index.cfm?ID=1978&#38;rand=31&#38;pid=1977&#38;TopicName=Understanding_distributed_data" rel="nofollow"&gt;GDB Geodatabase Replication&lt;/a&gt;

Cheers,

Dave</description>
		<content:encoded><![CDATA[<p>Not to be an ESRI &#8220;fan boy&#8221; (as Sean Gilles would call me), but this is one reason that I really like the new geodatabase replication that&#8217;s coming with ArcGIS 9.2 - you can cascade data between organizations, bi-directionally, at the database level. Since you have all the data locally, and it&#8217;s kept in synch with the original source, your application is not dependant on the uptime of the remote service. Of course this functionality is not &#8220;free&#8221;, but it&#8217;s better than relying on inconsistent services for mission criticla datasets</p>
<p>Here&#8217;s a link to the web help about <a href="http://webhelp.esri.com/arcgisdesktop/9.2/index.cfm?ID=1978&amp;rand=31&amp;pid=1977&amp;TopicName=Understanding_distributed_data" rel="nofollow">GDB Geodatabase Replication</a></p>
<p>Cheers,</p>
<p>Dave</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 1.163 seconds -->
