Project

General

Profile

Bug #13766

OGCAPI: make async

Added by Philippe May almost 3 years ago. Updated almost 3 years ago.

Status:
New
Priority:
Normal
Assignee:
Philippe May
Target version:
-
Start date:
11/03/2022
Due date:
% Done:

0%

Close

Description

When the WMS3 capabilities were set up, pygeoapi was not ready for async.

The intention was to prove the concept - which it did - and hoping that users would leverage the power of this capability.

Not only this did not happen, but the blocking nature of this non-async libraries might cause issues, when bots (GoogleBot) pass by and finally block the threads. The connection to the postgres database might then be severely impacted.

History

#1 Updated by Philippe May almost 3 years ago

A new project that seems to be a valuable replacement for pygeoapi: https://github.com/microsoft/ogc-api-fast-features .

This depends on fastapi, whereas Gisaf currently use aiohttp. ogc-api-fast-features docs mention that it's not tightly coupled for the backend (presumably PostGis).

However, a transition from aiohttp to fastapi seems to be possible for Gisaf (fastapi was chosen for treetrail and so far gives satisfaction).

Also available in: Atom PDF