elm-lang/websocket

Issues

• Clarify there is currently no native websocket support in Elm

  #30 opened 5 years ago by andys8
  1

• Support binary websockets?

  #9 opened 9 years ago by Daenyth
  6

• elm 0.19.0 upgrade

  #29 opened 6 years ago by mrumkovskis
  2

• Support Authorization header

  #21 opened 8 years ago by benjamin-bergia
  2

• This is completely broken in current elm?

  #28 opened 6 years ago by Gastove
  4

• Elm 0.19 release

  #27 opened 6 years ago by optikfluffel
  1

• Multiple open connections when subscription changes quickly

  #23 opened 8 years ago by Keyamoon
  1

• Support specifying subprotocol

  #20 opened 8 years ago by aymanosman
  2

• Internal server error when downloading 1.0.2 release

  #25 opened 7 years ago by igna92ts
  1

• Exponential backoff does not work

  #17 opened 8 years ago by bgourlie
  3

• Websocket exponential backoff is not randomized

  #26 opened 7 years ago by drathier
  1

• Support sending ordered list of messages

  #22 opened 8 years ago by cdevienne
  1

• Add subscriptions for connection opened and connection closed.

  #14 opened 8 years ago by bgourlie
  7

• Provide some way of checking for support

  #15 opened 8 years ago by Xandaros
  1

• API is missing notification of reconnect thus unnecessarily limiting its utility

  #10 opened 9 years ago by igoodrich
  0

• Error being swallowed when trying to open a websocket with a `#` character in its url

  #11 opened 9 years ago by davoclavo
  0

• Bug in 0.17 alpha - Websocket.listen in Child Component loses the appropriate Msg Tagging erratic results

  #4 opened 9 years ago by knowthen
  4

• Bug in 0.17 alpha - Calling Websocket.send in Http.App.program's init doesn't work, the WebSocket message is never sent

  #3 opened 9 years ago by knowthen
  1

• Fallback for unsupported API

  #5 opened 9 years ago by roine
  1

• subMap in WebSocket module - dead code?

  #6 opened 9 years ago by Janiczek
  1