Opened 22 years ago
Closed 21 years ago
#117 closed defect (fixed)
[WMS Client] Run WMS requests in parallel instead of sequentially
| Reported by: | dmorissette | Owned by: | dmorissette |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | WMS Client | Version: | 4.0 |
| Severity: | normal | Keywords: | |
| Cc: | mcilhagga@… |
Description
In the current implementation of WMS client support, the WMS requests are performed in sequential order. This means that the request to download layer2 doesn't start until layer1 is finished downloading, and so on. As a result of this, maps rendering time with multiple WMS layers is the sum of the rendering and download time of the individual layers. We should make the required changes in MapServer to fire all the WMS layer requests in parallel (this is possible with proper use of the libwww event loop), and then the map rendering time will be only affected by the layer that takes the longest time to download.
Change History (2)
comment:2 by , 21 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
| Version: | 3.6 → 3.7 |
Fixed. This has been implemented in 3.7 a little while ago.
Note:
See TracTickets
for help on using tickets.
