-
Notifications
You must be signed in to change notification settings - Fork 305
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
websockets test not working at all #49
Comments
Hello Pablo, Thanks for reporting this; I'm closing it as a duplicate of #49, let's keep the conversation there. Regards, Nicolas |
Hi Nocolas This issue you closed is the #49. Which one does it duplicate? Pablo On 07/06/2012 12:17 AM, Nicolas Favre-Felix wrote:
|
What is the expected output of
When I run, it without webdis I get :
When I shut down webdis while it is running I get :
When I shut down redis while it is running I get :
|
websocket not working is turning to a big issue for me :-/ |
does this just not work at the moment? that would explain it! please give a heads up if i can see this work!! thank you i dig this concept |
whoa! if i just run webdis instead of the websocket program, the websocket.html page loads everything up fine. (i did set websockets to true in the .json) I think you should remove the websocket program, unless I just dont understand what its for.. it lead to two afternoons of confusion, hoho! |
(NB: Newbie here) Similar to this, I modified the test to issue a SUBSCRIBE and I get back a subscribe reply as expected and then the websocket closes straight away. I was expecting it to stay up similarly to issuing the same SUBSCRIBE through a webbrowser where it stays open and recieves data as PUBLISH commands are issued. What am I missing? var jsonSocket = new WebSocket("ws://127.0.0.1:7379/.json"); Console output: JSON socket connected! test.html:55 |
Does commit 2cfc27d fix this? |
When testing the webdis build of "Jul 1 22:41:04 2012" with Redis 2.5.11 on Ubuntu 11.04 I've found that the websockets tests doesn't work at all.
Running the websocket test gives this result:
Opening the websocket.html page shows the "loading" message but nothing happens.
Other tests work fine, so I don't believe it has to do with redis itself and, to the extend of what I understand of webdis, the websocket in a fully webdis side mechanism, which doesn't rely on any redis support.
Regards
Pablo
The text was updated successfully, but these errors were encountered: