Skip to content

Milestones

List view

  • Features that break protocol compatibility with Drawpile 2.3.x, so are slated for inclusion into 2.4.0.

    No due date
    0/1 issues closed
  • Things belonging in the next server version of Drawpile. * Split the server into a frontend that users initially connect to and a backend providing the actual session hosting. This would allow for load balancing, graceful restarts and running multiple servers on the same host using different hostnames. * Cleaning up the login flow in the client. Currently, it supports two different flows depending on the server version, which makes the state machine immensely hard to comprehend. * Getting rid of the bespoke TCP protocol and using WebSockets for everything. This would allow using much HTTP tooling around proxying, tunneling etc.

    No due date
  • Features that break protocol compatibility with Drawpile 2.2.x, so are slated for inclusion into 2.3.0.

    No due date
    25/25 issues closed