We added the full package here:

https://sourceforge.net/projects/wurfl/ ... 20API/1.4/

Thanks

we asked the engineering team to produce a single all-inclusive download package too.

Please check back in a couple of days

Thank you

Hi there. We are thinking of leveraging the UA string to back populate the WURFL with the webkit version. This is not as straightforward as one might assume because there are a lot of different permutations of webkit browsers and we certainly don't want to get a bloated WURFL just to keep track of r...

dstricker wrote:
Does the tutorial you referred to exist yet [...]?

It does now. Enjoy.

http://www.scientiamobile.com/blog/post ... -with-JNDI

Pierre, unfortunately we don't speak french here, but we get the point of your msg. The asnwer is that versions of the WURFL APIs prior to 1.3 are no longer supported. Also, using such an old version today is basically pointless. The logic to handle Android and (partly) the iPhone is totally missing...

We need to think about this. We agree that leaving that value empty is not very elegant, but we don't want to change anything that may break how people are using WURFL today.

Anyway, stay tuned.

Thanks

Hi there, for webkit-based mobile browsers we have never explicitly assigned a browser version because there has never been a clear standard of what such a versioning number should be for all the different flavors of mobile webkit/safari out there. Historical reasons, if you will Those browsers can ...

We are planning a 1.4.1 release in a few weeks. We will make sure that this fix finds its way there. This issue is already fixed for Cloud users.

Thank you

wurfldb at scientiamobile.com (I am not using the '@' symbol in a mostly vain attempt to fool those freaking spammers)

thanks

I can confirm that this device is currently not in WURFL. The previous result was probably obtained with an older API. Older API were less precise and more likely to return false positives. API 1.4 will err on the side of telling you "I cannot tell you what this device is, except that it is Android ...

Which version of the wurfl.xml are you running? Can you send us a sample of the UA strings that are being recognized as generic? Are you sure that your UA strings aren't being modified? some servers (notably IIS) will distort the logged strings and make them vistrually useless for later analysis wit...

as far as we understand, the old ASP is deeply, totally and fundamentally incompatible with the new ASP.NET. So the answer is probably negative. Not sure if someone has come up with "bridge" solutions. In that case, you'll need to figure them out how to wrap the C# API autonomously. We also have a C...

I am sorry but your question does not make enough sense to attempt an answer. Can you try to explain what you mean again?

If English is an issue, you may want to try http://translate.google.com to translate from your native language to English...

Thank you

I have good news and bad news. The bad news is that Opera Mini will replace the UA string with its own. The good news is that you can often find the original UA string in a different header (x-operamini-phone-ua, if my memory serves me well). This means that you can still use the WURFL API to detect...

that Web Service has been removed because it had been deployed in breach of the WURFL license.

You can use the ScientiaMobile WURFL Cloud instead. We have a free offering for two capabilities and up to 5000 detections:

http://www.scientiamobile.com/cloud

Thank you, Emmanuel. You are absolutely right. The correct value should be -1. We will get it fixed ASAP

for commercial licensees, we release weekly snapshots (updates) of the WURFL DB.

We are working on the packaging of all 4 APIs. If everything goes smooth, we will release at the end of this week

Elrichar, the problem will be solved in the next wurfl.xml snapshot

Thank you

Next week. We are still not sure whether we will release it to the community right away, or will allow commercial licensees to get access to it in advance of everyone else.

I downloaded and change the jar file with the 1.3.6 and it works for Firefox 10 but for earlier version like 3.6 it fails: This is the user agent: mozilla/5.0 (windows; u; windows nt 5.2; en-us; rv:1.9.2.16) gecko/20110319 firefox/3.6.16|5.0 (Windows; en-US)|Win32 Thanks, Simon Simon, something is ...