>
Different Methods For Flash Player Detection in a ...
Welcome, Guest

by pooja on Thursday, 19 November 2009
Different Methods For Flash Player Detection in a Browser


Flash content—whether interactive games, advertising, flexible messaging, video programming, or commerce-based applications—runs on the Flash Player. The version of the Flash Player required to view your content needs to be installed on the end user’s computer. There are three methods to detect the Flash Player Version. To detect the Flash Player version, you select and customize a detection method.

Client-side scripting detection : This method uses JavaScript to check for the existence of a Netscape plug-in or an ActiveX control, and provides the logic for either displaying your Flash content or initiating an installation of the correct player version. Because the Flash Player exists as both a browser plug-in and an ActiveX control, a combination of different JavaScript routines is needed to properly check for the player. ActiveX installation is used in Internet Explorer, while Netscape, Firefox, Safari, Opera and other browsers support browser plug-ins.

In this method, you first create functions for script-based detection of the ActiveX control and the plug-in. These two functions will be called by another function that returns the version number of the user’s installed Flash Player. That function calls the ActiveX detection function if the user is running Internet Explorer under Windows. Otherwise it calls the JavaScript detection function.
Depending on the version number retrieved, the client-side script proceeds in one of the following ways:
• If the retrieved version number indicates the right Flash Player is installed, the <object> and <embed> tags for your content will be written to the page and your content will be shown to the user.
• If the user has an older version of Flash Player installed or if no Flash Player is detected at all the user will be shown the alternate content, including a link to the Get Flash web page on the Adobe web site.

Use script-based detection when:
• Script-based detection can be used when deploying Flash content to modern browsers and operating systems.
• If you want to display alternate content based on the configuration of end users’ computers and browsers, script-based detection can determine version and configuration information that is not detectable by other methods.

Avoid scriptbased detection when:
• While generally reliable, scriptbased detection will fail if the browser loading the content has had scripting disabled. For the rare occurrences where scripting is disabled, Macromedia recommends using the <noscript> HTML tag to display alternate content.
• While increasingly uncommon, some older browsers do not support scripting (for example, the Macintosh versions of Internet Explorer 4.0 and earlier). If older browsers are important to distributing your content, you will need to detect the browser version and display alternate content suitable for the browser’s display capabilities.


ActionScript-based detection : This method uses a Flash SWF file to detect which version of the player is installed and redirects the end-user to the Adobe Flash Player installation if their player needs to be updated.
Use ActionScript detection when:
• You only need to target end users who have Flash Player 4.0r11 (revision 11) or greater installed.
• Browser redirects are not a problem on your web site.
Avoid using ActionScript detection when:
• Flash Player is not installed on the end users’ computers.
• If browser redirects are a problem for your web site (for example, to redirect the user to the Flash Player installation page). When you would prefer to display alternate content inline rather than directing end users to a different page to install the Flash Player.


Server-side detection : This method creates a server-side application to determine which version of Flash Player is installed. If you are familiar with server-side development languages such as ColdFusion, PHP, or others, you can create a server side application to determine which version of Flash Player is installed using the mime-type information included in the HTTP_ACCEPT header information. To do this, users must have Flash Player 6.0r65 (revision 65) or later installed. With the release of Flash Player 6, the Flash mime-type “application/x-shockwave-flash” was added to the client HTTP_ACCEPT header. The HTTP_ACCEPT header is sent to the server each time a web page is requested, and includes information on all mime-types the browser can accept. If the user’s computer has Flash Player 6.0r65 (revision 65) or later installed, the “application/x-shockwave-flash” entry is added to the request header.

Use server-side code to detect Flash when:
• You expect users to have Flash Player 6.0r65 or later.
• You want a server-side implementation as part of a dynamic web site.

Avoid server-side code to detect Flash when:
• You do not have access to server-side scripting resources.
• You want to target users with versions of the Flash Player older than Flash Player 6.

 



Blogger Image
My Blog Title

Product Engineering, software engineering company, Product Development, Product Migration, Product Re-engineering, Product Maintenance, Product Testing Commercial Application Development, Business Software development, commercial software for startups, Application Support and Maintenance, software testing Product Maintenance, Outsource product maintenance, product support and maintenance Product Migration, Product Re-engineering, product re-engineering services Product Research, Product Engineering, UI Prototyping Services Software Testing Services, Quality Assurance services, professional software testers, Load Testing, Functional Testing, Cross Platform, Browser Testing, Test Automation, Testing Tools, software quality analysis Functional Testing Services, software quality analysis, Software Testing Services, Application Testing Services, Functional Testing Types Automated Testing, Automated Testing Services, automation testing, test script development, Automation Test Tools, outsource automation testing Load Testing, Performance Testing Services, Load Testing Tools Offshore Software Development, Outsource software services, offshore outsourcing services, offshore software development services, IT outsourcing services, software quality assurance services, Offshore IT services, Custom Application Development Services, Offshore Product Engineering Benefits of IT Outsourcing, Offshore Software Development companies, offshore software development firms Outsource planning, IT outsourcing, IT development services, offshore IT companies, offshore software development Offshore Software Development, Outsource software services, offshore outsourcing services, offshore software development services, IT outsourcing services, software quality assurance services, Offshore IT services, Custom Application Development Services, Offshore Product Engineering Offshore Software Development, Outsource software services, offshore outsourcing services, offshore software development services, IT outsourcing services, software quality assurance services, Offshore IT services, Custom Application Development Services, Offshore Product Engineering