Changes between Initial Version and Version 1 of Ticket #1377
- Timestamp:
- Jun 22, 2010, 12:31:45 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #1377 – Description
initial v1 1 1 This is the section about versions negotiation in WMS specification[[BR]] 2 2 [[BR]] 3 1. If a version unknown to the server and higher than the lowest supported version is requested, the server should send the highest version tosupports that is less than the requested version.3 1. If a version unknown to the server and higher than the lowest supported version is requested, the server should send the highest version it supports that is less than the requested version. 4 4 [[BR]] 5 5 [[BR]] 6 2. If a version lower than any of those known to the server is requested, then the server shall 6 2. If a version lower than any of those known to the server is requested, then the server shall send the lowest version it supports. 7 7 [[BR]] 8 8 [[BR]] 9 So, for the current implementation of OgcServer in webTier, there's a potential issue for an unknown version whichjust greater than the lowest supported version and less than any other supported versions.9 So, for the current implementation of !OgcServer in webTier, there's a potential issue for an unknown version which is just greater than the lowest supported version and less than any other supported versions. 10 10 [[BR]] 11 For example, MapGuide support 1.0.0 and 1.1.0. if there's a 1.0.5 request, MapGuide should reply a 1.0.0. However, the response is the highest version in cuurent implementation.11 For example, MapGuide support 1.0.0 and 1.1.0. if there's a 1.0.5 request, MapGuide should reply a 1.0.0. However, the response is the highest version in the current implementation. 12 12 [BR]] 13 13 [[BR]] 14 MapGuide already support edall the possible versions of WMS, nervertheless it's still a potential issue.14 MapGuide already supports all the possible versions of WMS, nervertheless it's still a potential issue.
