You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WFS 3.0 does not require a timeout on a request. How should a compliance test respond if a request takes an exceptionally long time to respond, or doesn't respond at all? One option would be to provide a user configurable timer. The timer would start whenever a request is issued. It would be stopped when the response is received. If the timer expires, then the service took too long to respond and that information would be recorded in the test report.
The text was updated successfully, but these errors were encountered:
dstenger
transferred this issue from opengeospatial/ets-ogcapi-features10
Oct 21, 2019
WFS 3.0 does not require a timeout on a request. How should a compliance test respond if a request takes an exceptionally long time to respond, or doesn't respond at all? One option would be to provide a user configurable timer. The timer would start whenever a request is issued. It would be stopped when the response is received. If the timer expires, then the service took too long to respond and that information would be recorded in the test report.
The text was updated successfully, but these errors were encountered: