Skip to content

Latest commit

 

History

History
46 lines (42 loc) · 2.42 KB

ROADMAP.md

File metadata and controls

46 lines (42 loc) · 2.42 KB
Raw

Roadmap

Done

  • Subscription
  • Fix data race on timer management
  • Message dispatch to client using the library (publish message received are dispatched)
  • Basic publish support
  • Support reset of timer when sending a packet from client
  • Implement unsubscribe
  • Implement disconnect
  • Make connect synchronous. It is easy in Go to wrap the call to make it asynchronous: http://stackoverflow.com/a/6329459/559289
  • Reconnect with backoff strategy (basic)
  • Central place for errors definitions
  • Ability to set clientID.
  • Handle teardown & reconnect from either sender or receiver.
  • Support persistent session option
  • Use new Marshaller: Preallocate buffer of correct size in marshallers to improve performance (+buffer write can return errors).
  • Rename PDU to a name more in line with MQTT specification.
  • Address go vet + various other linter
  • Manage Packet ID during session.
  • Keep the subscription state in the client
  • Basic TLS support with username / password authentication. Two address scheme are used: tcp or tls.

TODO

  • Add missing QOS 1 and 2 control packets.
  • QOS 1 and 2
  • Send queue to send changes that were not acked.
  • Internal library architecture diagram (with go routines and channels)
  • errcheck: check that all required errors are handled properly (errcheck)
  • Support timeout on PingResp to trigger reconnect
  • Ability to set session as persistent. If session is persistent, there is no need to resubscribe on reconnect if server say there were subscription (except inflight) See: http://www.hivemq.com/blog/mqtt-essentials-part-7-persistent-session-queuing-messages
  • Setup subscriptions after background reconnect if it was not a persistent session
  • Implement store interface and backend to ensure no message loss in client.
  • Use context to clean data flow ? (https://www.youtube.com/watch?v=3EW1hZ8DVyw&list=PL2ntRZ1ySWBf-_z-gHCOR2N156Nw930Hm)
  • Support subscription based on callbacks as an addition to channels ? Is that really needed ?
  • Authentication with username, password. They can be place in URL scheme. tcp://username:password@server
  • Certificate based authentication
  • Ability to configure TLS CA Roots to check against custom CA.
  • More unit tests
  • Example of publish / subscribe sharing Go structures with encoding/gob (RPC like)
  • Support command-line option for examples (to pass server, port, username, ...)
  • Support for MQTT-SN spec ? http://mqtt.org/new/wp-content/uploads/2009/06/MQTT-SN_spec_v1.2.pdf