Re: WebSockets app on CF
Dr Nic Williams <drnicwilliams@...>
Vinod, this means for PWS applications that you too will need different hosts for your websocket traffic, and make it a CNAME to the loggregator endpoint.toggle quoted messageShow quoted text
On Wed, Jun 22, 2016 at 6:54 AM +1000, "Dr Nic Williams" <drnicwilliams(a)gmail.com> wrote:
Nice detective work!
On Wed, Jun 22, 2016 at 6:29 AM +1000, "Shannon Coen" <scoen(a)pivotal.io> wrote:
The Ops team may have spun up an ELB just for websockets, so they can use a standard port in TCP mode.
$ dig loggregator.run.pivotal.io
loggregator.run.pivotal.io. 60 IN A 22.214.171.124
loggregator.run.pivotal.io. 60 IN A 126.96.36.199loggregator.run.pivotal.io. 60 IN A 188.8.131.52loggregator.run.pivotal.io. 60 IN A 184.108.40.206
$ dig api.run.pivotal.io
api.run.pivotal.io. 60 IN A 220.127.116.11
api.run.pivotal.io. 60 IN A 18.104.22.168
Shannon CoenProduct Manager, Cloud FoundryPivotal, Inc.
On Sun, Jun 19, 2016 at 6:28 PM, Dr Nic Williams <drnicwilliams(a)gmail.com> wrote:
The gorouter itself supports websocket connections. The "cf logs" streaming logs is one user of websockets.
How you access it might depend on which CF you target.
Look in ~/.cf/config.json for how "cf logs" accesses loggregator:
cat ~/.cf/config.json | grep Logg "LoggregatorEndPoint": "wss://loggregator.run.pivotal.io:443",
I'm actually surprised by the above - I thought PWS used port :4443 for websockets/loggregator.
On Mon, Jun 20, 2016 at 11:23 AM, Vinod Singh <vinoddandy(a)gmail.com> wrote:
Do you have any guidance/recommendations for running Web Sockets apps on Cloud Foundry ?
I am afraid that if application need to open multiple connections it may affect the performance of the overall system.
Any recommendation and pointer will help....
Dr Nic WilliamsStark & Wayne LLC - consultancy for Cloud Foundry usershttp://drnicwilliams.com
http://starkandwayne.comcell +1 (415) 860-2185