Dieses Repository beinhaltet HTML- und Javascript Code zur einer NotizenWebApp auf Basis von Web Storage. Zudem sind Mocha/Chai Tests im Browser enthalten. https://meinenotizen.netlify.app/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

CHANGELOG.md 4.0KB

4 years ago
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142
  1. ### 0.7.4 / 2020-05-22
  2. - Avoid crashing if `process.version` does not contain any digits
  3. - Emit `ping` and `pong` events from the `Server` driver
  4. - Require http-parser-js >=0.5.1 which fixes the bug we addressed in 0.7.3
  5. ### 0.7.3 / 2019-06-13
  6. - Cap version of http-parser-js below 0.4.11, which introduced a bug that
  7. prevents us from handling messages that are part of the same input buffer as
  8. the handshake response if chunked encoding is specified
  9. ### 0.7.2 / 2019-06-13
  10. (This version was pulled due to an error when publishing)
  11. ### 0.7.1 / 2019-06-10
  12. - Catch any exceptions produced while generating a handshake response and send a
  13. `400 Bad Request` response to the client
  14. - Pick the RFC-6455 protocol version if the request contains any of the headers
  15. used by that version
  16. - Use the `Buffer.alloc()` and `Buffer.from()` functions instead of the unsafe
  17. `Buffer()` constructor
  18. - Handle errors encountered while handling malformed draft-76 requests
  19. - Change license from MIT to Apache 2.0
  20. ### 0.7.0 / 2017-09-11
  21. - Add `ping` and `pong` to the set of events users can listen to
  22. - Replace the bindings to Node's HTTP parser with `http-parser-js`
  23. ### 0.6.5 / 2016-05-20
  24. - Don't mutate buffers passed in by the application when masking
  25. ### 0.6.4 / 2016-01-07
  26. - If a number is given as input for a frame payload, send it as a string
  27. ### 0.6.3 / 2015-11-06
  28. - Reject draft-76 handshakes if their Sec-WebSocket-Key headers are invalid
  29. - Throw a more helpful error if a client is created with an invalid URL
  30. ### 0.6.2 / 2015-07-18
  31. - When the peer sends a close frame with no error code, emit 1000
  32. ### 0.6.1 / 2015-07-13
  33. - Use the `buffer.{read,write}UInt{16,32}BE` methods for reading/writing numbers
  34. to buffers rather than including duplicate logic for this
  35. ### 0.6.0 / 2015-07-08
  36. - Allow the parser to recover cleanly if event listeners raise an error
  37. - Add a `pong` method for sending unsolicited pong frames
  38. ### 0.5.4 / 2015-03-29
  39. - Don't emit extra close frames if we receive a close frame after we already
  40. sent one
  41. - Fail the connection when the driver receives an invalid
  42. `Sec-WebSocket-Extensions` header
  43. ### 0.5.3 / 2015-02-22
  44. - Don't treat incoming data as WebSocket frames if a client driver is closed
  45. before receiving the server handshake
  46. ### 0.5.2 / 2015-02-19
  47. - Fix compatibility with the HTTP parser on io.js
  48. - Use `websocket-extensions` to make sure messages and close frames are kept in
  49. order
  50. - Don't emit multiple `error` events
  51. ### 0.5.1 / 2014-12-18
  52. - Don't allow drivers to be created with unrecognized options
  53. ### 0.5.0 / 2014-12-13
  54. - Support protocol extensions via the websocket-extensions module
  55. ### 0.4.0 / 2014-11-08
  56. - Support connection via HTTP proxies using `CONNECT`
  57. ### 0.3.6 / 2014-10-04
  58. - It is now possible to call `close()` before `start()` and close the driver
  59. ### 0.3.5 / 2014-07-06
  60. - Don't hold references to frame buffers after a message has been emitted
  61. - Make sure that `protocol` and `version` are exposed properly by the TCP driver
  62. ### 0.3.4 / 2014-05-08
  63. - Don't hold memory-leaking references to I/O buffers after they have been
  64. parsed
  65. ### 0.3.3 / 2014-04-24
  66. - Correct the draft-76 status line reason phrase
  67. ### 0.3.2 / 2013-12-29
  68. - Expand `maxLength` to cover sequences of continuation frames and
  69. `draft-{75,76}`
  70. - Decrease default maximum frame buffer size to 64MB
  71. - Stop parsing when the protocol enters a failure mode, to save CPU cycles
  72. ### 0.3.1 / 2013-12-03
  73. - Add a `maxLength` option to limit allowed frame size
  74. - Don't pre-allocate a message buffer until the whole frame has arrived
  75. - Fix compatibility with Node v0.11 `HTTPParser`
  76. ### 0.3.0 / 2013-09-09
  77. - Support client URLs with Basic Auth credentials
  78. ### 0.2.2 / 2013-07-05
  79. - No functional changes, just updates to package.json
  80. ### 0.2.1 / 2013-05-17
  81. - Export the isSecureRequest() method since faye-websocket relies on it
  82. - Queue sent messages in the client's initial state
  83. ### 0.2.0 / 2013-05-12
  84. - Add API for setting and reading headers
  85. - Add Driver.server() method for getting a driver for TCP servers
  86. ### 0.1.0 / 2013-05-04
  87. - First stable release