Currently there is a very basic structure for sending and receiving packets as a client conforming to the MQTT protocol 3/3.1.1 We need a proper implementation of all MQTT 3/3.1.1 requests and responses. Some smaller issues from this:
Of course, all MQTT 3/3.1.1 functionality
Elegant way to send and receive packets
Elegant way to send/receive packets in a way that supports customizability
Mostly I'm looking for discussion on the best way to handle this. Currently, I'm thinking to have one class represent each type of packet that can be sent by code or decoded from the socket. I'm looking to maybe have a more elegant way to asynchronously process incoming packets/send packets. Currently a simple ScheduledExecutor is used.
Currently there is a very basic structure for sending and receiving packets as a client conforming to the MQTT protocol 3/3.1.1 We need a proper implementation of all MQTT 3/3.1.1 requests and responses. Some smaller issues from this:
Mostly I'm looking for discussion on the best way to handle this. Currently, I'm thinking to have one class represent each type of packet that can be sent by code or decoded from the socket. I'm looking to maybe have a more elegant way to asynchronously process incoming packets/send packets. Currently a simple ScheduledExecutor is used.
MQTT 3.1.1 SPEC