Log message:
www/ruby-faye-websocket: update to 0.11.2

0.11.2 (2023-04-04)

* Handle SSL certificate chains where not all the intermediate certificates
  are recognised by the client

Log message:
www: Replace RMD160 checksums with BLAKE2s checksums

All checksums have been double-checked against existing RMD160 and
SHA512 hashes

Not committed (merge conflicts):
www/nghttp2/distinfo

Unfetchable distfiles (almost certainly fetched conditionally...):
./www/nginx-devel/distinfo array-var-nginx-module-0.05.tar.gz
./www/nginx-devel/distinfo echo-nginx-module-0.62.tar.gz
./www/nginx-devel/distinfo encrypted-session-nginx-module-0.08.tar.gz
./www/nginx-devel/distinfo form-input-nginx-module-0.12.tar.gz
./www/nginx-devel/distinfo headers-more-nginx-module-0.33.tar.gz
./www/nginx-devel/distinfo lua-nginx-module-0.10.19.tar.gz
./www/nginx-devel/distinfo naxsi-1.3.tar.gz
./www/nginx-devel/distinfo nginx-dav-ext-module-3.0.0.tar.gz
./www/nginx-devel/distinfo nginx-rtmp-module-1.2.2.tar.gz
./www/nginx-devel/distinfo nginx_http_push_module-1.2.10.tar.gz
./www/nginx-devel/distinfo ngx_cache_purge-2.5.1.tar.gz
./www/nginx-devel/distinfo ngx_devel_kit-0.3.1.tar.gz
./www/nginx-devel/distinfo ngx_http_geoip2_module-3.3.tar.gz
./www/nginx-devel/distinfo njs-0.5.0.tar.gz
./www/nginx-devel/distinfo set-misc-nginx-module-0.32.tar.gz
./www/nginx/distinfo array-var-nginx-module-0.05.tar.gz
./www/nginx/distinfo echo-nginx-module-0.62.tar.gz
./www/nginx/distinfo encrypted-session-nginx-module-0.08.tar.gz
./www/nginx/distinfo form-input-nginx-module-0.12.tar.gz
./www/nginx/distinfo headers-more-nginx-module-0.33.tar.gz
./www/nginx/distinfo lua-nginx-module-0.10.19.tar.gz
./www/nginx/distinfo naxsi-1.3.tar.gz
./www/nginx/distinfo nginx-dav-ext-module-3.0.0.tar.gz
./www/nginx/distinfo nginx-rtmp-module-1.2.2.tar.gz
./www/nginx/distinfo nginx_http_push_module-1.2.10.tar.gz
./www/nginx/distinfo ngx_cache_purge-2.5.1.tar.gz
./www/nginx/distinfo ngx_devel_kit-0.3.1.tar.gz
./www/nginx/distinfo ngx_http_geoip2_module-3.3.tar.gz
./www/nginx/distinfo njs-0.5.0.tar.gz
./www/nginx/distinfo set-misc-nginx-module-0.32.tar.gz

Log message:
www: Remove SHA1 hashes for distfiles

Log message:
www/ruby-faye-websocket: update to 0.11.1

0.11.1 (2021-05-24)

* Prevent the client hanging if close() is called when already closing

Log message:
www/ruby-faye-websocket: update to 0.11.0

Update ruby-faye-websocket package to 0.11.0.

0.11.0 / 2020-07-31

* Implement TLS certificate verification and enable it by default on client
  connections
* Add a :tls option to the client with sub-fields :root_cert_file and
  :verify_peer for configuring TLS verification

Log message:
www/ruby-faye-websocket: update to 0.10.9

Update ruby-faye-websocket to 0.10.9.

pkgsrc changes:
* Add "USE_LANGUAGES=	# none".
* Update LICENSE to apache-2.0.

### 0.10.9 / 2019-06-13

- Use the EventMachine API rather than `IO#write` to write data; this uses the
  event loop and avoids getting blocked by slow clients

### 0.10.8 / 2019-06-10

- In the case of a close timeout, don't block on waiting for writing to the
  socket to complete
- Fix a race condition that caused a timeout not to be cancelled immediately
  when the WebSocket is closed
- Change license from MIT to Apache 2.0

Log message:
Update ruby-faye-websocket 0.10.7.

Upstream changes (from CHANGELOG.md):

### 0.10.7 / 2017-02-22

* Emit an error if `EventMachine::Connection#unbind` is called with an error

Log message:
Import ruby-faye-websocket-0.10.6 as www/ruby-faye-websocket.

faye-websocket is a general-purpose WebSocket implementation
extracted from the Faye project. It provides classes for easily
building WebSocket servers and clients in Ruby. It does not
provide a server itself, but rather makes it easy to handle
WebSocket connections within an existing Rack application.
It does not provide any abstraction other than the standard
WebSocket API.

It also provides an abstraction for handling EventSource connections,
which are one-way connections that allow the server to push data
to the client. They are based on streaming HTTP responses and can
be easier to access via proxies than WebSockets.