[Mapserver-users] WMS-GetMap problem in 4.0 (works in 3.6.6)

[Frieso ter Haseborg]

>-----Original Message-----
>From: Daniel Morissette [mailto:morissette at dmsolutions.ca]
>Sent: Wednesday, August 27, 2003 10:57 PM
>To: Frieso ter Haseborg
>Cc: mapserver-users at lists.gis.umn.edu
>Subject: Re: [Mapserver-users] WMS-GetMap problem in 4.0 (works in
>3.6.6)
>
>
>Frieso ter Haseborg wrote:
>> 
>> okay absolute path works. *whooops* 
>> 
>> I have to specify an absolute path in my client-map-file. 
>>But why? Why does this work with MS 3.6.6? 
>The handling of relative paths has changed between versions 
>3.6 and 4.0. 
>  It may be that you are running into a specific exception (or used to 
>take advantage of an exception).  If you consider this to be a bug you 
>could file it in bugzilla with a sample mapfile and a description of 
>your installed directory structure (i.e. where the mapfile is located, 
>where you expect ../tmp to be located, etc.) and we could investigate.

Hmm, still not sure - perhaps only a problem in a newbees head. ;-)

>> And why does the wms-server-map-file work
>> (using a relative path) when called directly?
>Because the WMS server doesn't need to write to the IMAGEPATH 
>directory, but the WMS client does.

>The WMS client writes the temporary images that it downloads from the 
>remote WMS server in the IMAGEPATH directory and deletes them 
>as soon as 
>it's done with them.  So you never see any files in the IMAGEPATH 
>directory in this case but it is being used.

Okay, so if I access a mapfile with local layers not working with that
template-stuff only performing getMap, no temp-files are needed and the
output is directly served to the clients browser - so IMAGEPATH isn't
used at all. 
On accessing a mapfile with wms-layer beside local layers the
wms-layer-image is temporary saved with the *.tmp-extension in IMAGEPATH
- so now the folder IS used.

So imagepath is only used when working with html-templates or wms-layers
in the mapfile. Correct?

TIA
Frieso