QGIS3 QGIS Server code sprint Notes

QGIS code sprint (almost) live!

14 developpers and contributors to QGIS and QGIS servers met in city of Lyon in France the 12 th and 13th december 2016

Common view

Just after coffee, a common brainstorming to share the global vision over QGIS server :

![Alt text]QGIS brainstorm

Work being done by each one:

Oslandia (Hugo Mercier)

QEP 74 from Martin Dobias over Qgis layer registry refactoring will bring multiple project support. Oslandia would like to work on a prototype

• get rid of the old map renderer (https://github.com/qgis/QGIS/pull/3809 by Paul Blottiere)
• avoid too much gui dependencies
• prototype
• finish pull request
• work on SLD FE
• Functionnality Matrix

3 Liz (David Marteau)

• architecture: NGINX + QGIS server cluster

  • deploy cluster of fcgi apps sucks
  • hacking around plugins to get syslog logging
  • Server cache invalidation not working over NTFS (inotify problem).

• RABBITMQ + qgis server cluster

  • fcgi not applicable
  • Embedding is very basic (no control over I/O)

• Qgis server Services as pllugins like providers

• python loader

• response object

  • should be python compliant
  • enable streaming
  • do not presume HTTP being the protocol response format
  • Provide I/O falicities

• implemented: abstract interfaces / service registry / native loader

• Work in Progress

  • python loader
  • Tests
  • Write Services

See https://github.com/dmarteau/QGIS

Heavy discussion on plugin architecture

boundless Alessandro Passotti request for an external cache to allow scaling / load balancing system each qgis instance should be able to centralize cache (qgis server node farm use case) to avoid cache duplication

Discussion,"do we need a project cache? " why not just export a binary blob when saving qgs project? No more xml parsing then.

Tracking of what is done during Code sprint

1. https://github.com/qgis/QGIS/pull/3809 - replace QgsMapRenderer has been merged. During this work Paul noticed that multithread rendering on server side worked, but that all tests failed. One hypothesis is that tests are not compatible with multithread rendering. If that's verified, we could expect huge performance improvements on rendering! A good candidate for day-2 work.