Re: WebSockets app on CF


Dr Nic Williams <drnicwilliams@...>
 

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 54.209.4.129
loggregator.run.pivotal.io. 60 IN A 54.164.226.148loggregator.run.pivotal.io. 60 IN A 54.85.214.51loggregator.run.pivotal.io. 60 IN A 52.72.122.104
$ dig api.run.pivotal.io

api.run.pivotal.io. 60 IN A 52.1.229.72
api.run.pivotal.io. 60 IN A 52.72.101.87
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:
Friends, 
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....
Regards,Vinod




--
Dr Nic WilliamsStark & Wayne LLC - consultancy for Cloud Foundry usershttp://drnicwilliams.com
http://starkandwayne.comcell +1 (415) 860-2185
twitter @drnic

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.