Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info
iconfalse
titleThis page has been translated automatically

We want to provide you with the latest help content in your language as soon as possible. This page has been translated automatically and may contain grammatical errors or inaccuracies. We want this content to be useful to you. Please let us know at the bottom of this page if this information was helpful.

View the original article in Russian: Π£ΠΏΡ€Π°Π²Π»Π΅Π½ΠΈΠ΅ ΠΏΠΎΠ΄ΠΊΠ»ΡŽΡ‡Π΅Π½ΠΈΡΠΌΠΈ Π² Mozilla Firefox

Process-level connection management

For one reason or another, you may need to change the standard behavior of our Firefox browser, restrict its work, or, conversely, speed it up. One of the important parts of a browser is a new pagedealing with connections.

Firefox has a number of connection settings, such as:

  • network.http.max-connections - maximum number of concurrent active HTTP connections per process;

  • network.http.max-persistent-connections-per-proxy - maximum number of concurrent connections via HTTP proxy per domain;

  • network.http.max-persistent-connections-per-server - the maximum number of simultaneous connections without a proxy, or through a SOCKS proxy per domain;

  • network.http.pipelining - using pipelining without a proxy. If the server supports pipelining, then several requests to the server can be processed simultaneously through one connection of your computer;

  • network.http.proxy.pipelining - similarly using pipelining with a proxy;

  • network.http.pipelining.maxrequests - the maximum number of pipeline requests.

Depending on the power of your computer and the bandwidth of the Internet channel, you can change the restrictions, both up and down.

In ZennoPoster, the default browser configuration looks like this:

Code Block
pref("network.http.max-connections", 16);
pref("network.http.max-persistent-connections-per-proxy", 8);
pref("network.http.max-persistent-connections-per-server", 8);
pref("network.http.pipelining", false);
pref("network.http.proxy.pipelining", false);
pref("network.http.pipelining.maxrequests", 1);

Instance-level connectivity management

ZennoPoster uses the division of the process into instances, in this case the standard settings of connection restrictions apply in total to all instances at once. In this regard, in version 5.11.2.0, special settings were introduced that operate in tandem with the standard ones:

  • network.http.max-connections-per-instance - maximum number of concurrent active HTTP connections per instance;

  • network.http.max-persistent-connections-per-proxy-per-instance - the maximum number of simultaneous connections via HTTP proxy per instance;

  • network.http.max-persistent-connections-per-server-per-instance - the maximum number of simultaneous connections without a proxy, or through a SOCKS proxy per instance.

By default, these settings are set to 0 and are ignored.

If you want to change these settings in your template, then use the C # snippet:

Code Block
instance.SetBrowserPreference("network.http.max-connections-per-instance", 2 );
instance.SetBrowserPreference("network.http.max-persistent-connections-per-proxy-per-instance", 2 );
instance.SetBrowserPreference("network.http.max-persistent-connections-per-server-per-instance", 2 );

Thus, now you can customize the Firefox browser in ZennoPoster more precisely.