FireFox with SSL

[RebootExpert]

I agree UserMain having the lowest priority. But each XHR request will take about 500ms to complete both in firefox and chrome. I can see the SSL/TLS connection negotiation time is about 100ms in the FireFox developer tools panel. Also the XHR request will abort if it's not complete before the next request.
FireFox

firefox_request_time.png (127.21 KiB) Viewed 4051 times

Chrome

chrome_request_time.png (87.29 KiB) Viewed 4051 times

The ssl and tcp are have enough socket available to use, even during the delay.

main_loop.png (73.13 KiB) Viewed 4051 times

[RebootExpert]

Even though the web server have the higher priority over the UserMain to run, during those delay xhr request can't establish a connection with server. what could possible stop the server from working with more than enough socket available to use

[RebootExpert]

Plus I also test that after the webpage loaded, I wait for 5 minutes to start xhr request . once I start request, it hang immediately. So I don't think it's the negotiation cause all these.

[Jon]

HI RebootExpert,

I'm going to be testing your posted app later today and will post something as soon as I have the results. =)

Kind Regards,
Jon

[RebootExpert]

As I look into http vs websocket comparison http periodic polling is not recommended. Websocket seems to be a good solution to this. Plus the server wouldn't be powerful enough to handle the requests from multiple https webpage. I will learn and try to build an app use websocket to see if the problem still . However I am not sure if NB support websocket over SSL. If you can still look at my provided app that will be a great help.

[Jon]

We do support secure websockets. When you call Connect, you can use one of two functions. In both, the last parameter determines whether or not the connection should be secure:

int WebSocket::Connect( IPADDR host, const char * resource, int portnum, bool useSSL )
int WebSocket::Connect( const char * host, const char * resource, int portnum, bool useSSL )