See #25 - this would allow e.g. a custom security layer to be injected based on the partition metadata (and maybe document header?). The partition metadata should then contain access control information for the given partition/stream, so that needs to be specified at stream creation time. This only works with the default partitioning scheme on streams and not with arbitrary partitionings.
Note though that this requires giving an additional context argument to all read/write API unless it should depend on global state.