var client = MQTTClient.Factory.Build();
await client.ConnectAsync();
await client.PublishAsync( topic: "test", payload: Array.Empty<byte>(), QualityOfService.AtLeastOnce);IO.Pipelines are not easy to use, and at the time I'm writing this, the XML Docs are scarce in details. So I compiled some reading for you. First thing to read: https://docs.microsoft.com/en-us/dotnet/standard/io/pipelines When should you flush the pipe ? dotnet/runtime#26747 (comment)
More tests !
Sync QoS0 publish ?
Remove the ValueTask<Task> in the publish, instead return a result, which:
- Contain a method that return a task to await for the ack
- Will contain fields for MQTT5 Auth packets of MQTT5.
Session related things doesn't work well. Split regular/advanced API in the namespaces.
An exception outside the try/catch in the input loop doesnt kill the client. Cancel all tasks if reconnecting with new connection. (behavior, "throw if lost session" ?) Determine when the store must have storing guarenties, and when we don't care that it stored right now the data. Sync => we don't care that the data is stored right now. Async => must be stored when async end. Currently this is not checked: MQTT-1.5.3-1 The character data in a UTF-8 encoded string MUST be well-formed UTF-8 as defined by the Unicode specification [Unicode] and restated in RFC 3629 [RFC3629]. In particular this data MUST NOT include encodings of code points between U+D800 and U+DFFF. If a Server or Client receives a Control Packet containing ill-formed UTF-8 it MUST close the Network Connection
Write test where we send more than IdStore(startCount) packets.
Fixes namespaces. Fixes all accessibility modifier to what it should be. IInputLogger contain Client Reflex loggers. It cause the Server to have
Logger methods match their context (after refactoring that may not be the case anymore).
A doc per project. A good readme. All public API documented.
Useless alloc: instead of allocating Publish object I could just write them directly into a buffer and queue it.