Jay Klehr

The `*netfront/3.1*`/`*netfront/3.5*` ones are somewhat interesting and probably not something that can be fixed with any sort of ordering (since one of the optimizations in the pattern cache is to...

@mimmi20 Sure, will do.

I actually hadn't re-run the full list of agents since making some of the sorting tweaks (btw, the sorting that I mention I had to change from ascending to descending,...

Aside from those Symbian agents that I already looked at, here's my analysis as to why `browscap-php` selects a different pattern for the other user agents in that list: Agentbrowscap-php...

After some more testing, and a bit of a look at the php source for the `get_browser` function I've got `browscap-php` parsing that list of useragents as close as I...

This is the branch that I've put together that has the work I've done to try and get `browscap-php` to match `get_browser`. https://github.com/jaydiablo/browscap-php/tree/accuracy-test-dual-length As mentioned above, there are still 16...

I've been able to shave another ~10 seconds off that parse time for the browscap test suite agents, which puts this branch at about 43 seconds vs. the original's 27...

This branch (https://github.com/jaydiablo/browscap-php/tree/accuracy-test-dual-length-word-filter) extends on the work I did earlier to get the accuracy of the parser down to only 13 differing useragents (same as before). It adds a word...

I ran all three (`get_browser`, `browscap-php` 3.0 and my branch of `browscap-php`) against 50,000 unique "real world" useragents (from our logs over past 30 days). `browscap-php` 3 parsed 94 differently...

@mimmi20 No, this is a different list, the 50,000 was taken from our server logs for the last 30 days. The other ~47,000 list was taken from test suites of...