<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7233.69">
<TITLE>Is OpenLayers client-side only?</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><FONT SIZE=2 FACE="Arial">I'm hoping to have a couple architectural questions cleared up. Mainly, is OpenLayers purely a client-side ajax package? Or does it include components that run on the server as well?</FONT></P>
<P><FONT SIZE=2 FACE="Arial">As I currently understand it, setting up a web-based map (using my own map rather than Google or Yahoo etc) will involve:</FONT></P>
<P><FONT SIZE=2 FACE="Arial">o installing UMN MapServer on a server to handle the actual map data</FONT>
<BR><FONT SIZE=2 FACE="Arial">o installing ka-map on a server to handle tiling functionality</FONT>
<BR><FONT SIZE=2 FACE="Arial">o including OpenLayers in the script of a web page</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">This way, OpenLayers runs in the browser and accesses ka-map tiling code running on the server, which in turn calls MapServer.</FONT></P>
<P><FONT SIZE=2 FACE="Arial">Is this correct? Is ka-map currently a useful and/or desirable piece of this puzzle? Are there any diagrams or descripts you that could help clear this up?</FONT></P>
<P><FONT SIZE=2 FACE="Arial">Thanks for any help!</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">Charlie</FONT>
</P>
</BODY>
</HTML>