On 6/16/14 04:54, ale...@mozilla.com wrote:
Returning the issuer as part of the 302 on GET /call/{token} [0]
This is not compatible with the fact we try to not do a 302 anymore [1] in
order to a) avoid a roundtrip b) have urls such as http:/
On Mon, Jun 16, 2014 at 12:50 PM, Tarek Ziadé wrote:
> Le 16/06/14 11:54, ale...@mozilla.com a écrit :
> > ..
> >> Maximum Simultaneous Connections 11,656,238
> > Current max sockets connections on an EC2 host is 250K. This means we'll
> > need approx. 46 servers to handle the long term max sim.
On 6/16/14 14:50, Tarek Ziadé wrote:
Le 16/06/14 11:54, ale...@mozilla.com a écrit :
..
Maximum Simultaneous Connections 11,656,238
Current max sockets connections on an EC2 host is 250K. This means we'll
need approx. 46 servers to handle the long term max sim. connections.
...
This seems
Le 16/06/14 11:54, ale...@mozilla.com a écrit :
> ..
>> Maximum Simultaneous Connections 11,656,238
> Current max sockets connections on an EC2 host is 250K. This means we'll
> need approx. 46 servers to handle the long term max sim. connections.
The RAM is possibly the driving factor here - depen
(reposting with better formatting, the list didn't liked HTML)
Thanks Adam;
Here are a couple of remarks / comments about what's proposed in the
document:
Returning the issuer as part of the 302 on GET /call/{token} [0]
This is not compatible
Thanks Adam;
Here are a couple of remarks / comments about what's proposed in the
document:
Returning the issuer as part of the 302 on GET /call/{token} |0]
This is not compatible with the fact we try to not do a 302 anymore
[1] in order to a) avoid a roundtrip b) have urls such as
[1]
6 matches
Mail list logo
