Meetings2011-09-08 » History » Version 8
Version 7 (J. Moringen, 09/08/2011 05:04 PM) → Version 8/13 (Anonymous, 09/08/2011 05:15 PM)
h1. Meetings 2011-09-08
h2. C++ again: @InformerBase@, @AnyType@ and @uncheckedPublish@
* #521
* Type/scope checks
** Disabling should be possible regardless of the configuration mechanism
** As quality of Service option?
*** Can be enabled for debugging
** Efficiency improvements
*** Hash type names for faster comparison?
h2. RST
* Current State (Jan)
* Suggestions
** To reduce footprint of built libraries
*** Include only relevant data types in built libraries
*** Domain-specific libraries?
*** If possible, provide the complete data-type library and smaller partial libraries
**** Should be a build-time option to avoid runtime redundancy
**** Drawback: redundant linking causes hard-to-debug problems
** Converters should be built into "framework-specific" libraries
*** Example: one shared library for OpenCV converters
* CitCatalog BETA (Florian)
** Catalog online and connected to LDAP - https://citbox.cit-ec.uni-bielefeld.de
** Entities:
**# System
**#* Top in the catalog hierarchy
**# Components
**#* Metadata: Author, Tags, ..., free text
**#* Can be linked to publications and open data
**# Publications
**#* References to PUB via PUBID (automatically imported from PUB)
* Discussion
h2. Performance Enhancements (and "Threadless RSB")
* New event processing strategies
** Associated configuration
* Improvements in @Scope@ class
* Transports
** Improvements in in-process transport
** Improvements in Spread transport
** New Socket-based transport
h2. Language-specific Configuration?
* #551
h2. C++ again: @InformerBase@, @AnyType@ and @uncheckedPublish@
* #521
* Type/scope checks
** Disabling should be possible regardless of the configuration mechanism
** As quality of Service option?
*** Can be enabled for debugging
** Efficiency improvements
*** Hash type names for faster comparison?
h2. RST
* Current State (Jan)
* Suggestions
** To reduce footprint of built libraries
*** Include only relevant data types in built libraries
*** Domain-specific libraries?
*** If possible, provide the complete data-type library and smaller partial libraries
**** Should be a build-time option to avoid runtime redundancy
**** Drawback: redundant linking causes hard-to-debug problems
** Converters should be built into "framework-specific" libraries
*** Example: one shared library for OpenCV converters
* CitCatalog BETA (Florian)
** Catalog online and connected to LDAP - https://citbox.cit-ec.uni-bielefeld.de
** Entities:
**# System
**#* Top in the catalog hierarchy
**# Components
**#* Metadata: Author, Tags, ..., free text
**#* Can be linked to publications and open data
**# Publications
**#* References to PUB via PUBID (automatically imported from PUB)
* Discussion
h2. Performance Enhancements (and "Threadless RSB")
* New event processing strategies
** Associated configuration
* Improvements in @Scope@ class
* Transports
** Improvements in in-process transport
** Improvements in Spread transport
** New Socket-based transport
h2. Language-specific Configuration?
* #551