<!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.7653.38">
<TITLE>Local App Vs Service WRT PAGC</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><SPAN LANG="en-ca"><FONT SIZE=2 FACE="Arial">To address some comments form the previous threads,</FONT></SPAN>
</P>
<P><SPAN LANG="en-ca"><FONT SIZE=2 FACE="Arial">The issue of online versus offline…</FONT></SPAN>
</P>
<P><SPAN LANG="en-ca"><FONT SIZE=2 FACE="Arial">From the perspective of PGAC (</FONT></SPAN><A HREF="http://www.pagcgeo.org/"><SPAN LANG="en-ca"><U><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">http://www.pagcgeo.org/</FONT></U></SPAN></A><SPAN LANG="en-ca"><FONT SIZE=2 FACE="Arial">) it is obvious both of these are possible with one library.</FONT></SPAN>
</P>
<P><SPAN LANG="en-ca"><FONT SIZE=2 FACE="Arial">The first implementation of PAGC wa sa command line application. The current incarnation is now a library. Ontop of the library is built an OGC compliant web service based application. But the ability to implement a command line interface is still very possible I would imagine.</FONT></SPAN></P>
<P><SPAN LANG="en-ca"><FONT SIZE=2 FACE="Arial">So the important point here is that if you have a (fast) library that crunches the heavy workload and then the interface can either be web based, command line, or imbeded into an application… So developers can create what ever they want.</FONT></SPAN></P>
<P><SPAN LANG="en-ca"><FONT SIZE=2 FACE="Arial">Cheers</FONT></SPAN><SPAN LANG="en-us"></SPAN>
</P>
</BODY>
</HTML>