Image Cache

[KIERAN AMES]

I've waited for more than a year to be able to do the things I've done in
just the past few days! By all means, "Carry on!" .
(I just worry about the "assuming it'll compile on NT" part of your reply.
Brent has been great help. Dare I ask for more???)

    <PETRIFIED>
        shiver, shiver; worry, worry. Then, what'll I do??
    </PETRIFIED>

Kieran

Stephen Lime wrote:

> You could hack mapserv.c and have it spit out
> the tag you mention. Another way would be to
> come up with a more unique naming convention.
> Version 3.3 now uses time + pid for what should
> be a truly unique name. If you can hold out for a
> few more days your problem should be solved,
> assuming it'll compile on NT. ;-)
>
> Steve
>
> <<< "KIERAN AMES" <kames at keyspanenergy.com> 11/ 4  1:04p >>>
> I've installed a port of Mapserv onto a NT4.0 machine and am now
> experimenting. I've run across an implementation problem with regard to
> images being cached.
>
> I believe that image names are created with the map name concatenated to
> the processID. In NT, process IDs don't run very high and are re-used.
> Therefore, when a new image is created, the client browser sees an image
> name and if it finds it in its local cache, it doesn't fetch the revised
> image that was just created.
>
> I can control this in regular cgi (Perl) by sending non-parsed headers
> and delivering a "Pragma:No-cache" line in the http headers. Is there an
> equivalent solution with MapServ on an NT platform?
>
> Thanks very much.
> Kieran Ames
>
> PS. I'm new to MapServ, but I think its GREAT!