<html st="" repl="http://schemas.microsoft.com/repl/" ss="urn:schemas-microsoft-com:office:spreadsheet" z="urn:schemas-microsoft-com:" sp="http://schemas.microsoft.com/sharepoint/" x="urn:schemas-microsoft-com:office:excel" w="urn:schemas-microsoft-com:office:word" xsi="http://www.w3.org/2001/XMLSchema-instance" v="urn:schemas-microsoft-com:vml" xmlns="http://www.w3.org/TR/REC-html40" s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xsd="http://www.w3.org/2001/XMLSchema" q="http://schemas.xmlsoap.org/soap/envelope/" p="urn:schemas-microsoft-com:office:powerpoint" o="urn:schemas-microsoft-com:office:office" oa="urn:schemas-microsoft-com:office:activation" m="http://schemas.microsoft.com/office/2004/12/omml" wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" d="DAV:" c="urn:schemas-microsoft-com:office:component:spreadsheet" pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" b="urn:schemas-microsoft-com:office:publisher" a="urn:schemas-microsoft-com:office:access" rs="urn:schemas-microsoft-com:rowset" rtc="http://microsoft.com/officenet/conferencing" x2="http://schemas.microsoft.com/office/excel/2003/xml" dir="http://schemas.microsoft.com/sharepoint/soap/directory/" dsss="http://schemas.microsoft.com/office/2006/digsig-setup" dsp="http://schemas.microsoft.com/sharepoint/dsp" ex12t="http://schemas.microsoft.com/exchange/services/2006/types" dssi="http://schemas.microsoft.com/office/2006/digsig" spwp="http://microsoft.com/sharepoint/webpartpages" sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" udc="http://schemas.microsoft.com/data/udc" udcxf="http://schemas.microsoft.com/data/udc/xmlfile" ois="http://schemas.microsoft.com/sharepoint/soap/ois/" udcp2p="http://schemas.microsoft.com/data/udc/parttopart" sps="http://schemas.microsoft.com/sharepoint/soap/" ec="http://www.w3.org/2001/04/xmlenc#" dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" ds="http://www.w3.org/2000/09/xmldsig#" mrels="http://schemas.openxmlformats.org/package/2006/relationships" odc="urn:schemas-microsoft-com:office:odc" mver="http://schemas.openxmlformats.org/markup-compatibility/2006" ppda="http://www.passport.com/NameSpace.xsd" udcs="http://schemas.microsoft.com/data/udc/soap" html="http://www.w3.org/TR/REC-html40">
<head>
<style type="text/css">
<!--
body { margin-right: 4px; margin-left: 4px; font-variant: normal; margin-top: 4px; margin-bottom: 1px; line-height: normal }
li.msonormal { font-size: 11.0pt; margin-right: 0in; margin-left: 0in; font-family: Calibri,sans-serif; margin-top: 0in; margin-bottom: .0001pt }
span.emailstyle17 { color: black; font-family: Calibri,sans-serif }
a:visited { text-decoration: underline; color: purple }
p { margin-top: 0; margin-bottom: 0 }
span.msohyperlink { text-decoration: underline; color: blue }
span.msohyperlinkfollowed { text-decoration: underline; color: purple }
a:link { text-decoration: underline; color: blue }
p.msonormal { font-size: 11.0pt; margin-right: 0in; margin-left: 0in; font-family: Calibri,sans-serif; margin-top: 0in; margin-bottom: .0001pt }
div.msonormal { font-size: 11.0pt; margin-right: 0in; margin-left: 0in; font-family: Calibri,sans-serif; margin-top: 0in; margin-bottom: .0001pt }
-->
</style>
</head>
<body lang="EN-US" link="blue" vlink="purple">
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">All,</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">Interesting idea. It would be a method for collecting resources from multiple domains too. I assume the GET part of the operation would be from the MapServer side?</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">To push this idea somewhat . . . :c) Any need by anyone to have the MapServer output head out to a new service?, not really an include per-se, but more of a pipelining thing. My need here would be for syncing a remote instance of mapserver with a master version somewhere on the internet.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">bobb</font> </p>
<br> <br><br>
<p style="margin-bottom: 0; margin-top: 0">
<br>
<br>
>>> "Lime, Steve D (DNR)" <Steve.Lime@state.mn.us> wrote:<br> </p>
<div style="margin-right: 0; margin-left: 15px; margin-top: 0; background-color: #f3f3f3; padding-left: 7px; border-left: solid 1px #050505; margin-bottom: 0">
<div class="section1">
<p style="margin-bottom: 0; margin-top: 0" class="msonormal">
Hi all: Was chatting with Brent F. a bit about dynamic mapfile content. One idea that surfaced was URL-based includes, e.g.:<o p="#DEFAULT"></o> </p>
<p style="margin-bottom: 0; margin-top: 0" class="msonormal">
<o p="#DEFAULT">
 </o> </p>
<p style="margin-bottom: 0; margin-top: 0" class="msonormal">
  INCLUDE “<a href="http://.../some%20file%20or%20CGI%20script">http://.../some file or CGI script</a>”<o p="#DEFAULT"></o> </p>
<p style="margin-bottom: 0; margin-top: 0" class="msonormal">
<o p="#DEFAULT">
 </o> </p>
<p style="margin-bottom: 0; margin-top: 0" class="msonormal">
Any thoughts on the utility of such a function? Code would have to be added into the lexer section that handles includes. Could just write whatever is retrieved in a temp directory and then open as normal.<o p="#DEFAULT"></o> </p>
<p style="margin-bottom: 0; margin-top: 0" class="msonormal">
<o p="#DEFAULT">
 </o> </p>
<p style="margin-bottom: 0; margin-top: 0" class="msonormal">
Steve<o p="#DEFAULT"></o> </p>
<p style="margin-bottom: 0; margin-top: 0" class="msonormal">
<o p="#DEFAULT">
 </o>
</p>
</div>
</div>
</body>
</html>