OT: limit number of connections from browser to my server?

[Grant Edwards]

On 2016-05-17, Gregory Ewing <greg.ewing at canterbury.ac.nz> wrote:

> Is there some way you can get more stuff into a single
> html page? For example, use inline css and image data
> instead of delivering them as separate files.

Yes.  That's one option that's still on the table, and that's probably
what the smart money is betting on: use server-side includes for css
and javascript files.  For image data, I'd need to add a
server-side-include-and-base64-encode capability, but that shouldn't
take more than a couple hours.


Then the HTML editing starts...

I've seen examples of including base64 image data in HTML <img> tags,
but don't know how to do it in CSS for things like backgrounds.

That said, I've got two more things to try to see if I can convince
browsers to behave:

 1) Stall the connection after the TCP connection opens but before the
    SSL handshake.

 2) Try listen(0) on my BSD-derived network stack to limit the number
    of TCP connections.  IIRC, BSD behaves differently than Linux when
    the listen queue overflows.

I doubt either one will help -- and even if they do, it'll probably
all fall apart again when new browser versions come out.

I'm also looking into SSL session resumption.  My SSL stack appears to
support it, but I can't tell if it's being used or not by browsers.

It may be a moot point.  All of the descriptions I've read about SSL
session resumption say it's for low-overhead reopening of a previously
closed connection.  That's not what I need: I need to speed up opening
of a new connection while the first connection is still open.

-- 
Grant Edwards               grant.b.edwards        Yow! Mary Tyler Moore's
                                  at               SEVENTH HUSBAND is wearing
                              gmail.com            my DACRON TANK TOP in a
                                                   cheap hotel in HONOLULU!