websockets
Here are 2,504 public repositories matching this topic...
Dear developers. I write my custom specific web server for work with specific archive files, compression, encryption, etc. And i want to publish my web server under BSD-2-Clause license.
In my project i use Iris and Iris logger as basement.
I'm not going to use the name of your project to promote my project.
Can I publish my project under the BSD-2-Clause license?
Thanks.
The background image on the website doesn't look that great (due to high jpeg compression) and doesn't tile properly on large screens.
Here's a better way: http://qrohlf.com/trianglify/
-
Updated
May 27, 2020 - C++
The feature list on the documentation is wrong. It refers to a missing feature. See at:
https://github.com/actix/actix-web/blob/206733188478f4d18df376a72fac3a4938b99bd6/src/lib.rs#L79
I found that when looking for a way to disable to client build.
Is your feature request related to a problem? Please describe.
gdb features, such as whether reverse debugging is enabled, is currently guessed at by gdbgui.
Describe the solution you'd like
use -list-feature instead of guessing gdb's features
The Readme lists under features "Local or remote cursor". As far as I can tell this option was disabled and Remote cursors will be used whenever they are available. However, on view only connections the users see no cursor with buttons being clicked by an invisible cursor.
I was able to fix this by changing these two lines
In _negotiate_server_init:
this._display.disableLocalCursor()
-
Updated
May 17, 2020 - Go
See http://blog.erlang.org/ssl-logging-in-otp-22/ for a full description.
One could enable debug logging in Cowboy to see all the packets transmitted and what Cowboy thinks of them, something like that. Could make some client issues obvious in particular.
Hello, I'm updating from 3.1.0 to 4.0.3.
Do we have some documentation available (more advance guide than README.md)? More precisely about WebSocketDelegate?
I don't really know what I should do when these methods are called:
case .viabilityChangedor
case .reconnectSuggestedWhat the point of them?
I can see viabilityChanged is called when we loss an
The official Widgets Development Guide only contains the most basic widget types as example.
There is no functional example for a Flot chart in there right now. Or is it?
Since this is one of the most useful and probably used (at leat to me) widgets it would be very helpful to extend that docum
This is wonderful work and I'm very grateful to find this repo. I'm having difficulty understanding how to scale to multiple networks following the SCC guide and also confused on the recommended architecture. The main issue is clients on separate servers are not finding messages from each other.
On a gcloud instance, i start the state (node server.js), broker( SCC_STATE_SERVER_HOST='[google giv
The links on the FAQ page in the wiki still point to the old wiki, which seems to be deprecated.
In the docs about supporting binary messages, it is stated that the controller should implement Ratchet\WebSocket\MessageComponentInterface.
However, if using Ratchet\App, when adding a new route with this controller, the WsServer is not created, since the [`$controller instanceof MessageComponentInterfa
The "routing" docs page doesn't mention that Route() is for HTTP only and WebSocketRoute() is required for websocket endpoints. I found WebSocketRoute through examples on other pages but it woudl be good if it was fully described on the "routing" page.
-
Updated
May 23, 2020 - Python
-
Updated
May 27, 2020 - Java
-
Updated
Jul 2, 2018 - Java
I've the websockets server working absolutely fine with supervisor. However, I found out that it stops sending messages every ~3 days. My first line of action is to adjust this setting as suggested in the documentation:-
[supervisord]
minfds=10240; (min. avail startup file descriptors;default 1024)
I'm going to observe what happens. But even after reading the documentation; I can
-
Updated
May 22, 2020 - C++
A Spring Boot user has reported a problem with Spring Boot's reference documentation linking to Jetty's documentation. Spring Boot's reference documentation links to the Jetty documentation for the specific version of Jetty that it built against. For example, the documentation for Spring Boot 2.2.4 links to https://www.eclipse.org/jet
I'm trying to implement object oriented Websocket client and server. Since websockets is completely coroutine based, I'm finding it difficult to go ahead with implementation. Is it possible to wrap it around classes? Are there any examples of using it in this way?
-
Updated
May 13, 2020 - TypeScript
-
Updated
May 22, 2020 - C++
-
Updated
May 27, 2020 - C
https://www.boost.org/doc/libs/1_71_0/libs/beast/doc/html/beast/using_websocket/timeouts.html says
The timeout features of the TCP or basic stream should not be used when working with a websocket stream.
and
`The timeouts on the websocket stream are incompatible with the timeouts used in the tcp_stream. When constructing a websocket stream from a tcp stream that has timeouts enabled, th
To encourage people to use wss/tls encryption, we should make it really simple for people to implement a signed cert using letsencrypt.org (which should be going into general availability in the next couple of months). Perhaps direct automatic integration (since that's one of the goals of Let's Encrypt), but at least, we should document a straightforward process for using it.
The process is docum
Thank you for HTTP, and thank you for the recent additions of the logging and event logging system - they were very easy to use, and very helpful.
I've been investigating a problem in my system where requests are being sent to a server that is being s
-
Updated
May 27, 2020 - PHP
Improve this page
Add a description, image, and links to the websockets topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the websockets topic, visit your repo's landing page and select "manage topics."
Looks closely related to #779
I'm submitting a...
Current behavior
Middleware is being called for every endpoint a request route could potentially match.