Opened 15 years ago
Closed 15 years ago
#2921 closed defect (invalid)
Keep the mapObj alive across subsequent FastCGI requests
| Reported by: | hobu | Owned by: | sdlime |
|---|---|---|---|
| Priority: | normal | Milestone: | 6.0 release |
| Component: | MapServer FastCGI | Version: | unspecified |
| Severity: | normal | Keywords: | |
| Cc: | assefa |
Description
This bug will be used to track work related to keeping mapObj's alive across subsequent FastCGI requests.
Change History (2)
comment:1 by , 15 years ago
| Component: | MapServer C Library → MapServer FastCGI |
|---|
comment:2 by , 15 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
This bug is dead. The ultimate driver of this was the performance need that was solved by the proj4 caching. With that in place, there's no need to complicate things by trying to keep a mapObj alive.
Note:
See TracTickets
for help on using tickets.
Howard: Who should own this? Not me I think... Moving to the *new* FastCGI component.
Steve