Type: Integer
Specifies the number of milliseconds a browser has to finish retrieving a datastream in the background of approximately 50KB in size. If the browser does not finish in this time period, it is categorized by the Broadband property as a dial-up connection. Otherwise it is categorized as a broadband connection. The default value for this property is 1500, which represents 1.5 seconds.
Most broadband connections should finish retrieving the datastream in less than one second. However poor quality broadband connections, such as those with speeds under 300Kbps or those with very high latency (which can occur with some public wireless networks) may not finish retrieving the datastream in time, and therefore be categorized as a dial-up connection despite technically being on broadband.
If the Broadband property occasionally misidentifies visitors on poor broadband connections as being on dial-up, you can account for this by increasing the BroadbandMaxWait value. This will provide more time for the datastream to finish downloading.
The downside to increasing the BroadbandMaxWait property is that it increases the amount of time it takes for BrowserHawk to perform the Broadband test on dial-up users. By default this test takes no more than 1.5 seconds because BroadbandMaxWait is 1500 milliseconds.
As an example, if you increase this setting to 2500, it will now take 2.5 seconds instead of 1.5 seconds the broadband test to complete for all dial-up users. Note however that broadband users on decent quality connections will not experience any noticeable testing time, even with higher BroadbandMaxWait settings - the extra test time applies only to dial-up users.
The default setting of 1500 is quite aggressive and could lead to some misidentifications for reasons explained above. We chose this aggressive setting, however, because the primary goal of the Broadband property is to determine the connection type with minimal wait time for dial-up users. And, testing with this setting proved very reliable will all but the poorest broadband connections. That being said, a setting of 2000 or 2500 may provide the best results if you prefer to trade the extra second or so of testing time for dial-up users for better handling of users on poor broadband connections.
Note: If you change the BroadbandMaxWait, you must do so prior to calling the GetExtendedBrowser method as shown in the example below. Otherwise setting this property will have no effect.
Example:
In this example we check to see if the visitor is on a broadband connection. If so we redirect them to a different page on the site.
<%
ExtendedOptions options = new ExtendedOptions();
options.AddProperties("Broadband");
ExtendedBrowserObj extBrow = BrowserObj.GetExtendedBrowser(options);
if (extBrow.Broadband == false) {
Response.Redirect("/slowpage.aspx");
}
%>
<html> Page for broadband users goes here </html>
See Also: