<html>
<head>
</head>
<body style="line-height: normal; font-variant: normal; font-weight: normal; margin-left: 4px; font-family: Comic Sans MS; margin-top: 4px; font-style: normal; margin-bottom: 1px; font-size: 12pt; margin-right: 4px">
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">Stephen,</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">I don't see this type of URL substitution as being any more latent than running a WMS (with SLD) request (same thing right??), especially if it's run through MapServer directly. We've tried the Scripting process and while it worked, keeping the MapServer version up as they came out was a bit time consuming, not to mention trying to keep things portable. I'm not interested in adding another "thing" to the MapServer engine toolbox for set up. I would much rather see something like this be handled inside of MapServer proper.</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">I'm looking at the flexibility of having the option. I can certainly see something like this becoming a potential crutch for some developers as well. And so, I'm not entirely sold on the idea myself yet, that this is a proper solution. It's more of a flexibility issue in my mind. WMS is fine and all, but you can't (yet) do everything, that mapserver can do even though I use WMS services a lot more now than I used to.</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">I'm not so sure I would need to go to another server every time I needed to use this type of assembly, but I can sure see it coming in handy if I did. I'm also all about diiding processes up amongst the data maintainers. This type of capability has the potential to spread to maintenance aspects out and away from dependence on a single publishing point, almost cloud based if you will . . .</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">My last piece here, is if this is really turning into a standards question, should there be a discussion about making a complete standards compliant version of MapServer. I believe quite a bit of stuff could be stripped out of MapServer in this scenario. Mapserver has been my tool of choice for may years because of it's flexibility, and not necessarily it's standards compliance.</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">In the end, all good points that you brought up. Most of them I'm still pondering myself. It seems like a good idea on the surface, and I've not heard a really big gotcha in this thread yet about why it would be inherently bad.</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">bobb</font> </p>
<br> <br>
<p style="margin-top: 0; margin-bottom: 0">
<br>
<br>
>>> Stephen Woodbridge <woodbri@swoodbridge.com> wrote:<br> </p>
<table bgcolor="#f3f3f3" border="0" style="margin-left: 15px; margin-top: 0; margin-bottom: 0; margin-right: 0; font-size: 1em">
<tr>
<td>
<div style="border-left: solid 1px #050505; padding-left: 7px">
<p style="margin-top: 0; margin-bottom: 0">
Bob,<br><br>I think one of the developers would need to answer this. But here are<br>some thoughts to consider:<br><br>This introduces a lot of latency in the response, because you have to<br>make a socket request to another host, which needs to create a process<br>and service the request, and send the results back to you. Not to<br>mention what do you do if the host or connection are down or bad.<br><br>If you are just asking this because it is a tricky way to add parameters<br>to the request, then I would simply ask to have parametrized includes<br>especially if I could load all my parameters from an initial include<br>with a computed filename based on the<br><br>To some extent you can already do this at the layer level, we normally<br>call it a WMS layer ;)<br><br>Which brings up the other point of making a remote request for an<br>include, what is the likelihood that a remote hose is going to know<br>about the data sources on your host? Are you than going to want remote<br>access to the data also. Oh wait ... that is a WMS request. :)<br><br>Ok, sarcasm aside, it is an interesting idea, but I think it has more<br>potential issues then benefits, but htat is just my 2 cents.<br><br>-Steve W<br><br>On 10/3/2011 3:18 PM, Bob Basques wrote:<br>> All,<br>><br>><br>> Would adding in INCLUDEs from a URL be pushing it too much, as in:<br>><br>><br>> INCLUDE " /http://Myserver.com/cgi-bin/myscript.pl<br>> <<a href="http://Myserver.com/cgi-bin/myscript.pl">http://Myserver.com/cgi-bin/myscript.pl</a>>/ "<br>><br>><br>> Could pass in parameters like so . . .<br>><br>><br>> INCLUDE " /http://Myserver.com/cgi-bin/myscript.pl?A=first /<br>> <<a href="http://Myserver.com/cgi-bin/myscript.pl?A=first">http://Myserver.com/cgi-bin/myscript.pl?A=first</a>> thing&b=second<br>> thing&c=third thing . . . "<br>><br>><br>> bobb<br>><br>><br>><br>><br>><br>>  >>> "Smith, Michael ERDC-CRREL-NH" <Michael.Smith@usace.army.mil> wrote:<br>><br>> There is an RFC to have includes come from non-file connections<br>> (databases). It would be another option<br>><br>> <a href="http://mapserver.org/development/rfc/ms-rfc-74.html">http://mapserver.org/development/rfc/ms-rfc-74.html</a><br>><br>><br>> Mike<br>><br>> --<br>> Michael Smith<br>><br>> Remote Sensing/GIS Center<br>> US Army Corps of Engineers<br>><br>><br>><br>> On 10/3/11 2:51 PM, "Stephen Woodbridge" <woodbri@swoodbridge.com> wrote:<br>><br>>  >One idea regarding this that you might want to consider is the ability<br>>  >to put all the named parameters in an include file, then be able to<br>>  >include that file via a CGI parameter. So it might look like this:<br>>  ><br>>  ><br>>  >MAP<br>>  > INCLUDE "client-params-%client_id%.inc"<br>>  > ...<br>>  >END<br>>  ><br>>  >And then you could have parameter files like:<br>>  ><br>>  >client-params-27.inc<br>>  >client-params-123.inc<br>>  >etc.<br>>  ><br>>  >And these would include nothing but your SET ... commands.<br>>  ><br>>  >Then when requesting the map:<br>>  ><br>>  >/http://localhost/cgi-bin/mapserv?client_id=123&mode=map&map=/path/to/mapf<br>>  >ile.map&...<br>>  ><br>>  >This would make it very easy to manage a single mapfile for parameters<br>>  >that are different for each client/user.<br>>  ><br>>  >Obviously the client_id could be set via a cookie, or a wrapper script,<br>>  >or a session variable, or manually, etc.<br>>  ><br>>  >-Steve W<br>>  ><br>>  >On 10/3/2011 2:39 PM, reholl wrote:<br>>  >> I'm interested in working on capabilities along these lines. Are there<br>>  >> existing RFCs that touch on this? If not, perhaps one should be<br>>  >>created.<br>>  >><br>>  >> This overlaps some configuration ideas I've been mulling over. From the<br>>  >> original comment here about internal vars being handy for "/when the<br>>  >>same<br>>  >> layers are re-used for several customers who like to have a bit<br>>  >>different<br>>  >> styling for the same source data/" it occurs to me that a matrix or some<br>>  >> other constructs more complex than a flat list of internal variables<br>>  >>might<br>>  >> be called for -- provided they don't turn the mapfile and internal<br>>  >>mapserv<br>>  >> into spaghetti..<br>>  >><br>>  >> Jukka Rahkonen (have I ordered your name properly?), do you want to<br>>  >>start an<br>>  >> RFC on this?<br>>  >><br>>  >> To anyone -- would this conversation typically migrate over to 'dev' ?<br>>  >><br>>  >> Robert Hollingsworth<br>>  >><br>>  >><br>>  >> I agree that this is a request that comes up often. As usual we'd just<br>>  >> need someone to lead the effort.<br>>  >><br>>  >> On 11-10-03 12:12 AM, Rahkonen Jukka wrote:<br>>  >>> Hi,<br>>  >>><br>>  >>> Inspired by the Thomas Bonfort's rendering chain I have been thinking<br>>  >>>if<br>>  >>> we could have a native support for using internal mapfile variables.<br>>  >>>Now<br>>  >>> Thomas is setting for example a bunch of colours in a definition file<br>>  >>> which is converted into a real mapfile with python script and c<br>>  >>> preprocessor.<br>>  >>> <a href="http://mapserver-utils.googlecode.com/svn/trunk/README">http://mapserver-utils.googlecode.com/svn/trunk/README</a><br>>  >>> <a href="http://mapserver-utils.googlecode.com/svn/trunk/generate_style.py">http://mapserver-utils.googlecode.com/svn/trunk/generate_style.py</a><br>>  >>><br>>  >>> I would like to see a simple way for setting the variables directly in<br>>  >>>the<br>>  >>> mapfile, somehow like<br>>  >>> MAP<br>>  >>> SET "pedestrian_clr" "#fafaf5"<br>>  >>> SET "forest_clr" "#dcdcb4"<br>>  >>> SET "industrial_clr" "#ebe5d9"<br>>  >>> ....<br>>  >>><br>>  >>> And then later in the layers use<br>>  >>> LAYER<br>>  >>> .....<br>>  >>> COLOR %pedestrian_clr%<br>>  >>><br>>  >>> The internal variables could be interpreted only from the mapfile and<br>>  >>>they<br>>  >>> could not be altered by the web users.<br>>  >>><br>>  >>> Internal variable would help in maintaining big mapfiles with repeating<br>>  >>> styles like in the OpenStreetMap rendering case. Another use case is<br>>  >>>when<br>>  >>> the same layers are re-used for several customers who like to have a<br>>  >>>bit<br>>  >>> different styling for the same source data.<br>>  >>><br>>  >>> -Jukka Rahkonen-<br>>  >>><br>>  >><br>>  >> --<br>>  >> View this message in context:<br>>  >><a href="http://osgeo-org.1803224.n2.nabble.com/Feature-wish-Internal-mapfile-vari">http://osgeo-org.1803224.n2.nabble.com/Feature-wish-Internal-mapfile-vari</a><br>>  >>ables-tp6853853p6856070.html<br>>  >> Sent from the Mapserver - User mailing list archive at Nabble.com.<br>>  >> _______________________________________________<br>>  >> mapserver-users mailing list<br>>  >> mapserver-users@lists.osgeo.org<br>>  >> <a href="http://lists.osgeo.org/mailman/listinfo/mapserver-users">http://lists.osgeo.org/mailman/listinfo/mapserver-users</a><br>>  ><br>>  >_______________________________________________<br>>  >mapserver-users mailing list<br>>  >mapserver-users@lists.osgeo.org<br>>  ><a href="http://lists.osgeo.org/mailman/listinfo/mapserver-users">http://lists.osgeo.org/mailman/listinfo/mapserver-users</a><br>><br>> _______________________________________________<br>> mapserver-users mailing list<br>> mapserver-users@lists.osgeo.org<br>> <a href="http://lists.osgeo.org/mailman/listinfo/mapserver-users">http://lists.osgeo.org/mailman/listinfo/mapserver-users</a><br>><br><br>_______________________________________________<br>mapserver-users mailing list<br>mapserver-users@lists.osgeo.org<br><a href="http://lists.osgeo.org/mailman/listinfo/mapserver-users">http://lists.osgeo.org/mailman/listinfo/mapserver-users</a><br>
</p>
</div>
</td>
</tr>
</table>
</body>
</html>