Geoffroy Couprie

messages can come with a null payload now: https://github.com/apache/pulsar/commit/d55bc00f34a2fa763a3756fa0adbb1366ae319bd

Schema usage

1

we need a new design around serialization, deserialization, that would be pluggable with Pulsar's schema interface, and the schema registry

Documentation

5

we are still missing a lot of documentation, on method, fields, etc, and code examples along with them. add ``` #![warn(missing_docs)] #![warn(missing_doc_code_examples)] ``` to src/lib.rs to see how much

message router

2

this is used to tell a producer on which partition a message should go: https://pulsar.apache.org/api/client/2.7.0-SNAPSHOT/org/apache/pulsar/client/api/MessageRouter.html

right now it sends a message to the consumer engine's channel, and only waits for that channel to have sent the message

handle CommandCloseProducer messages when a namespace is unloaded

1

when a topic moves to another broker (example: unloading a namespace), we receive a `CommandCloseProducer` message, after which we should lookup again the topic and create again the producer. Right...

End to end encryption

1

along with batching and compression, messages can be encrypted, this should be supported for compatibility with other clients as well

The Java client's [BatcherBuilder](https://github.com/apache/pulsar/blob/master/pulsar-client-api/src/main/java/org/apache/pulsar/client/api/BatcherBuilder.java) can change the batching policy: instead of adding all messages in the same batch, we put messages in different batches depending on their ordering key: https://github.com/apache/pulsar/blob/2fd878a8f4bfdd5cffa7fa6450714ec1ad25f514/pulsar-client/src/main/java/org/apache/pulsar/client/impl/BatchMessageKeyBasedContainer.java

It is a feature present in other clients. See [ConsumerInterceptor](https://github.com/apache/pulsar/blob/master/pulsar-client-api/src/main/java/org/apache/pulsar/client/api/ConsumerInterceptor.java) and [ProducerInterceptor](https://github.com/apache/pulsar/blob/master/pulsar-client-api/src/main/java/org/apache/pulsar/client/api/interceptor/ProducerInterceptor.java). These objects can be added to consumers and producers to hook messages and acknowledgements methods, and modify them

should we provide a client for the Pulsar HTTP API, through which we can manage subscriptions, get statistics, etc?