Thank you for your interest. We have decided not to allow direct access to our cloud service via the RESTful API at this time, but rather, we encourage you to use our WURFL Cloud Clients. Is there a particular reason that you don't want to use the official client? We have a Python and Ruby client in...

Ok, we'll get to the bottom of it and get back to you ASAP.

Thanks for the message, we are looking into this now. In the meantime, do you know if this started when you updated the data, or the API?

Hi mbrans, I can appreciate your concern, but I can assure you that there is nothing in the API that will expose your configuration settings. The phpMyAdmin searches you're seeing are very common - we see thousands of requests per day on our public-facing webservers. If you are concerned about these...

Hi, Currently, the WURFL Cloud Service is provided in High Performance mode only, which means that most desktop web browsers are identified generically. We are evaluating improvements that we can make to increase the accuracy of desktop browser detection in the cloud services, but we do not currentl...

Ah I see. There have been improvements to both the desktop categorization code (SimpleDesktop) and the mobile matchers (particularly Android). What this means is that web traffic is faster and mobile traffic is slower but more accurate. In a mixed web/mobile environment (like we test in for internal...

Hi Robert, The API has been changed significantly, with many improvements made for accuracy and performance; however, the total performance difference depends largely on the type of traffic you are serving, and whether or not you have SIMPLE_DESKTOP_ENGINE_ENABLE = true in your config. With mostly m...

We've tried to reproduce the problem, but we are unable to. In our tests, the cache behaves properly. Here's the scenario: 1) A visitor requests your page, 2) A cache cookie is sent with the 2 WURFL capabilities, 3) You change your capabilities on scientiamobile.com, 4) The same visitor visits your ...

We are looking into your question and will respond soon.

Hi Jarkko,

Node.JS is on a short list of potential new WURFL Cloud Clients, but that's about all I can say at the moment

I'm not exactly sure what's going on there. I see you're running PHP 5.2, which should be fine. I did notice that the cache seems to be rebuilding each time I visit the page (or there is some other delay). Can you post your configuration? Also, can you put this at the top of the test page?: <?php in...

Hi David, You are both correct, you can safely comment 'JavaMidlet' out in the WurflConstants file, which will remove it from that matcher chain. Any UAs that fall through to the CatchAll may be matched as generic_midp_midlet as well, but this only applies to UAs that would not have matched to begin...

Thanks for the update. Your issue seems to be Java specific, and we are able to reproduce it here. We will find the solution and let you know once it's fixed.

We have been able to reproduce the problem on PHP 5.1, and have released an updated version (1.4.1) that should work fine. Please let me know if the problem remains.

Thanks for the post. We've added some bot rules that remove the vast majority of bots from counting towards detections, although it's not pushed into production quite yet. You are right that it would make things a lot faster if we did this client-side, but the problem is that we don't know what valu...

Hi Andy, I can confirm that the vast majority of your traffic (>95%) is coming from bots :) We are in the final stages of rolling out our logic that excludes bots from the detections count. We'll keep your detections limit increased until we resolve the issue. Meanwhile, we've noticed that your serv...

All the APIs are updated at the same time, so the detection results should be very similar between them. When you see generic in the results, it's because we weren't able to match both the device and OS version. The WURFL APIs return a generic match, like generic_android_ver4_0 instead of matching t...

Hi Andy, Thanks for the response. I can see the traffic coming from your servers quite clearly, but I think you are right that there is something else strange going on here. I will look into it and get back with you, but in the meantime, I will bump up your allowed detections so you are not automati...

I see, sorry for the confusion, we have two APIs for PHP, the "PHP API" and the "Database API" (formerly Tera-WURFL). The example I gave was for the PHP API. Here is the example for the Database API (which you are using): // Initialization only needs to happen once require_once realpath(dirname(__FI...

Hi, You can indeed do batch lookups with the PHP API. You should write a quick program to process all the user agents you've collected, something like this: // Initialization only needs to happen once $wurflApiDir = dirname(__FILE__).'/../WURFL'; $resourcesDir = $wurflApiDir.'/../examples/resources'...