Hello there.

I ran into your module a while ago, and I think you're able to make it much better using DB "drivers". What I mean is that instead of building the API around one source of data, in this case the browscap.ini file, a better approach would be to write the core, and have hooks to install DB drivers that fetch the data, and interact with base API calls.

One great source of mobile data is actually commercial, and called DeviceAtlas (http://www.deviceatlas.com). The data is ever changing and many companies use it for correctly sniffing many great details about the client. DeviceAtlas even provides a ready-made PHP class to get the relevant data from their data files.

If you want, please send me a message privately (browscap AT orientalsensation DOT com) and I will split the current code into a functional API, plus write the current driver + DeviceAtlas driver.

Thanks.

Comments

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

This seems fairly reasonable to me. Drupal in general aims to be flexible in what it does.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Title: Browsecap drivers » Make the user agent lookup a pluggable system so that site admins can use other databases

Better title.

devin carlson’s picture

devin carlson commented
Status: Active » Closed (won't fix)

Marking as won't fix; there have been no requests for this functionality over the past three years, specific modules have been developed for each user agent database and I'm guessing that all of the "browscap" modules will simply become plugins to the final Web Services and Context Core Initiative solution.