Hi All,
I've been testing alpha's implementation with web-sockets recently with great results. For all of my testing, I have been using a Redis windows service local to the server that the application was being hosted. I am trying to integrate the web sockets implementation into a very large app now and my client and I have decided to use a remote Unix server to host the Redis service separate from the server in which the application is hosted.
This is where my issues have started.
In the project properties of the web project of alpha, I am able to specify the Web-Socket implementation of Redis and subsequently specify the Redis services host, port and/or URL. No matter what host, URL or port I specify for the Redis implementation, the application seems to always ignore these web-socket settings in the project properties or publishing profile and assume that the web-socket is local to the applications server. If I'm working locally, the web-socket request URL will be "ws://localhost:6379/?id=9D8F32B2-9F3C-4FDC-8518-B784B7D1EDA2" or if I'm hitting my remote WAS application at testurl.com for example, the web-socket request URL will be "ws://testurl.com:6379/?id=9D8F32B2-9F3C-4FDC-8518-B784B7D1EDA2" regardless of what settings I specified for the Redis host or url.
Has anyone tried using the Redis web-socket implementation on a remote server separate from the server that the WAS resides and got it to respect their web-socket settings? Are there any other web-socket settings in the project that I'm not taking into consideration?
Any help or info on this will be greatly appreciated.
Thanks in advance for your time and input!
I've been testing alpha's implementation with web-sockets recently with great results. For all of my testing, I have been using a Redis windows service local to the server that the application was being hosted. I am trying to integrate the web sockets implementation into a very large app now and my client and I have decided to use a remote Unix server to host the Redis service separate from the server in which the application is hosted.
This is where my issues have started.
In the project properties of the web project of alpha, I am able to specify the Web-Socket implementation of Redis and subsequently specify the Redis services host, port and/or URL. No matter what host, URL or port I specify for the Redis implementation, the application seems to always ignore these web-socket settings in the project properties or publishing profile and assume that the web-socket is local to the applications server. If I'm working locally, the web-socket request URL will be "ws://localhost:6379/?id=9D8F32B2-9F3C-4FDC-8518-B784B7D1EDA2" or if I'm hitting my remote WAS application at testurl.com for example, the web-socket request URL will be "ws://testurl.com:6379/?id=9D8F32B2-9F3C-4FDC-8518-B784B7D1EDA2" regardless of what settings I specified for the Redis host or url.
Has anyone tried using the Redis web-socket implementation on a remote server separate from the server that the WAS resides and got it to respect their web-socket settings? Are there any other web-socket settings in the project that I'm not taking into consideration?
Any help or info on this will be greatly appreciated.
Thanks in advance for your time and input!
Comment