<html o="urn:schemas-microsoft-com:office:office" v="urn:schemas-microsoft-com:vml" xmlns="http://www.w3.org/TR/REC-html40" w="urn:schemas-microsoft-com:office:word">
<head>
<style type="text/css">
<!--
a:visited { text-decoration: underline; color: purple }
span.emailstyle17 { font-family: Arial; color: black }
li.msonormal { font-family: Times New Roman; margin-right: 0in; font-size: 12.0pt; margin-left: 0in; margin-bottom: .0001pt; margin-top: 0in }
a:link { text-decoration: underline; color: blue }
p.msonormal { font-family: Times New Roman; margin-right: 0in; font-size: 12.0pt; margin-left: 0in; margin-bottom: .0001pt; margin-top: 0in }
span.msohyperlink { text-decoration: underline; color: blue }
span.msohyperlinkfollowed { text-decoration: underline; color: purple }
div.msonormal { font-family: Times New Roman; margin-right: 0in; font-size: 12.0pt; margin-left: 0in; margin-bottom: .0001pt; margin-top: 0in }
-->
</style>
</head>
<body lang="EN-US" style="margin-right: 4px; margin-left: 4px; font-variant: normal; margin-bottom: 1px; line-height: normal; margin-top: 4px" link="blue" vlink="purple">
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">Bob,</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">All old school here, we built our own raster pyramids and make a new request every time, no caching because we want to have the option of making incremental zoom scales.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">We don't use Tiled layers at all becuse of the limitation in needing to use a stepped view zooming (Like Google) , we need to be able to see some things are very particualr scale values for example.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">The raster pyramiding is actually doing this stepped zooming, but in the storage of the rasters, not in the publishing of them. Since we only ever assemble four tiles per layer on the fly, we can predict very well what the performance should be like at all levels or scales of operation.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">We have also done some work on Load balancing the composite raster requests across many hardware servers with good results.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">With the right tunning you can make even a WMS respond very quickly, even for very large image requests.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">bobb</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<br>
<br>
>>> "Bistrais, Bob" <Bob.Bistrais@maine.gov> wrote:<br> </p>
<table border="0" bgcolor="#f3f3f3" style="margin-right: 0; font-size: 1em; margin-left: 15px; margin-bottom: 0; margin-top: 0">
<tr>
<td>
<div style="padding-left: 7px; border-left: solid 1px #050505">
<div class="Section1">
<p class="MsoNormal" style="margin-bottom: 0; margin-top: 0">
<font size="2" face="Arial"><span style="font-family: Arial; font-size: 10.0pt">I was wondering what anyone was doing, with regard to caching tiles or other ways to boost performance in GeoMoose applications?  While our current applications are performing well in GeoMoose, we’re looking ahead as applications get more complex and bloated with data.  Has anyone done anything with GeoWebCache, for example, or some other means?<o style="font-family: Arial; font-size: 10.0pt" p="#DEFAULT"></o style="font-family: Arial; font-size: 10.0pt"></span></font>
</p>
</div>
</div>
</td>
</tr>
</table>
</body>
</html>