deegree3 developer team meeting 2010-08-03
Protocol by: AndreasSchmitz
Attendees: MarkusSchneider, ChristianKiehle, AndreiIonita, JensPabel, AndreasSchmitz
1. WPS Client branch
The WPS client branch of AndreiIonita has now integrated all proposed changes. The process of comparing the different approaches can now be started. A discussion about the next steps will be initiated soon on the mailing list.
2. SOS
For the SOS work is being done to clean up the data stores, especially the binary store and the continuous store. Proper initialization is still missing, and there are no schemas for their configuration.
3. PostGIS FeatureStore
There are currently three approaches to map feature types to the database, relational, BLOB and a hybrid mode (which is a mix between BLOB and relational). Read-Only access does now work with all three approaches for the PostGIS feature store, and Insert transactions are being developed next.
4. WPS service
Initial work has been done to allow dynamic process loading. An SPI interface (ProcessManagerProvider/ProcessManager) has been developed to allow processes to be instantiated as needed. The details of the configuration are being discussed.
5. Security
The SecureProxy servlet is working in a basic version. It allows proxying of GET and POST requests, changes Get/Post OnlineResources (service endpoint definitions) to the local address, and authenticates users through the new authority SPI mechanism. The only authorization check that is currently being done (and integrated in the interface an authority must implement) is a check whether users are allowed to access the proxied service or not.
6. CRS axis order hell
In order to clean up the axis order hell, a flag has now been added to the CRS class to switch the behaviour. The default behaviour is now to respect defined axis orders for all identifiers, the switch can be used to force x/y order.
7. Binary XML/Fast Infoset
Research has been done to optimize the BLOB storage of XML fragments in the database (more precisely any internal storage). Binary XML offers twice the speed of normal XML parsing, using half the size, and can be used as a drop in replacement for XMLStreamReaders/Writers.