> Actually this was plan B, as a poor-man implementation of the filter > infrastructure. Plan A was that the block filters would materialize suddenly > in > someone's git tree.
OK, so let us summarize the options: a.) wait untit it materialize suddenly in someone's git tree. b.) add BlockFilter inside BDS c.) add filter callbacks to block bojs (job_type) d.) use BlockDriver as filter e.) use the current BackupInfo unless filters materialize suddenly in someone's git tree. more ideas?