|
Q
|
Using the bridge pages from my older ColdFusion software to get extended properties such as Flash seems somewhat inelegant. Is there any way around this?
|
|
A
|
ColdFusion versions prior to MX do not provide the 'hooks' needed from inside our component to perform the extended property checks. Therefore the only way to perform these checks prior to MX is by using an ASP page (known as a bridge page) to detect what you want and then redirect back to your ColdFusion script with the answers in the query string.
However if you are using ColdFusion MX you can use BrowserHawk4J to natively check extended properties directly in ColdFusion MX pages, without the need for any bridge pages. This is much more efficient and provides seamless browser detection within your CFMX environment.
See: this KB article for related information.
|
