Page 1 of 1

When is Bluebox Needed

Posted: 12 Nov 2008, 23:53
by willypow
If we plan to run Smartfox on a separate IP address from our web-server then I suppose we could run both Smartfox and the web-server on port 80. Would there be any need for Bluebox in this configuration?

Or if our site does not need SSL and we run the webserver on 80 and Smartfox on 443 on the same IP, would we likely have any need for Bluebox?

I am trying to make sure I am not overlooking something.

Posted: 17 Nov 2008, 09:07
by Lapo
Sorry for the delay.
If we plan to run Smartfox on a separate IP address from our web-server then I suppose we could run both Smartfox and the web-server on port 80. Would there be any need for Bluebox in this configuration?

Not both.
Only one service can be run on a TCP port. Our recommendation is to put the BlueBox (http) on port 80 and SFS on port 443 (https)

Posted: 17 Nov 2008, 14:29
by willypow
Even if they are being hosted on different machines?

Posted: 17 Nov 2008, 14:43
by Lapo
No in that case both can run on port 80.
Simply make sure to specify in your application that the bluebox resides on a different IP address. By default the API assume that the BBox is on the same address of SFS.

Posted: 17 Nov 2008, 14:47
by willypow
I'm sorry, I am not being clear. I was proposing that the web server was running on a different box than Smartfox. Would there be any need for BlueBox if Smartfox were able to run on port 80?

Posted: 17 Nov 2008, 15:56
by Lapo
Yes, even when running on port 80 a client might not be able to connect if he's behind a proxy server.
The BlueBox creates an HTTP tunnel that allows users unable to establish a persistent connection to use the server with very good (and fully configurable) performance.

Posted: 17 Nov 2008, 17:14
by willypow
I understand, thanks.