- From: <Lauri.K.Hirvonen@nokia.com>
- Date: Tue, 14 Jul 2009 12:29:18 +0200
- To: <karan.geddam@motorola.com>, <gavin.landon@gmail.com>
- CC: <public-mw4d@w3.org>
- Message-ID: <227455977C217E4C8E1B1E066A3C370D3A71AAC6BD@NOK-EUMSG-01.mgdnok.nokia.com>
Hello Gavin In the dotMobi's developer site: http:/mobiforge.com there is Discussion Forum. You can read it even if you are not (yet) registered user. There is one discussion area for: Device Detection. http://mobiforge.com/forum/developing/device-detection In there one person has made the question, what are the differences between WURFL, Device Atlas and Mobile.Browser files? He is one response to it: DeviceAtlas includes WURFL as one of its sources of information for some of its properties. It should be more or less obvious which ones can be mapped directly to/from WURFL ones, but there are quite a few that aren't in WURFL at all at all. Also, DeviceAtlas doesn't tell you anything it doesn't know. If WURFL doesn't know something, it will always return a value, regardless of its authenticity. If DeviceAtlas doesn't know something, it won't pretend that it does :) So, an empty value means "unknown" Daniel Hunt dotMobi You can learn from those questions asked in that Discussion Forum and replies given there. Also you can register to be mobiForge member (it is free) and then you can post questions to that discussion forum. Br. Lauri ________________________________ From: ext Geddam Karan Deep-KHWG64 [mailto:karan.geddam@motorola.com] Sent: 14 July, 2009 10:30 To: Gavin Landon; Hirvonen Lauri.K (Nokia-CIC/Espoo) Cc: public-mw4d@w3.org Subject: RE: Hello all Hi Gavin, Have you tried WURFL? Check http://wurfl.sourceforge.net/ if it resolves your need. Cheers Karan ________________________________ From: public-mw4d-request@w3.org [mailto:public-mw4d-request@w3.org] On Behalf Of Gavin Landon Sent: 13 July 2009 16:45 To: Lauri.K.Hirvonen@nokia.com Cc: public-mw4d@w3.org Subject: Re: Hello all Thank you. I have a question. I was looking at this site and they reference DeviceAtlas. In the examples of using DeviceAtlas they show all we pass is a UserAgent. Based on my short experience, the headers don't always tell you what the device is. For example: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.20) Gecko/20080829 Firefox/2.0.0.20<http://2.0.0.20> This User Agent did come from a HTC Touch phone, using SkyFire. How does DeviceAtlas handle this? The only way I can think of handling this is to know the name and header info for every company that does this type of service. As you well know that would be a maintenance nightmare. On Sat, Jul 11, 2009 at 3:02 PM, <Lauri.K.Hirvonen@nokia.com<mailto:Lauri.K.Hirvonen@nokia.com>> wrote: Hello Gavin, welcome to the Mobile Internet I know dotMobi well. I'm one of the founders. They have free developer site: http://mobiforge.com/ Look the chain of advice they offer: * Starting<http://mobiforge.com/Starting> * Designing<http://mobiforge.com/Designing> * Developing<http://mobiforge.com/Developing> * Testing<http://mobiforge.com/Testing> * Running<http://mobiforge.com/Running> For Multimedia and video look this page: http://mobiforge.com/developing/story/audiovideo-playback-streaming-support-mobile-devices The guide for "device detection" is done by W3C. dotMobi provides then the "parameters of most of the mobile devices" in their Device Atlas: http://deviceatlas.com/ When you register to be dotMobi developer (it is free) they get the free access to the Device Atlas. Br. Lauri ________________________________ From: public-mw4d-request@w3.org<mailto:public-mw4d-request@w3.org> [mailto:public-mw4d-request@w3.org<mailto:public-mw4d-request@w3.org>] On Behalf Of ext Gavin Landon Sent: 10 July, 2009 00:19 To: public-mw4d@w3.org<mailto:public-mw4d@w3.org> Subject: Hello all Hello all, I've just signed up and hope to learn a few things about Mobile detection via web. Background: I'm old C++ guys with 15 or so languages I've used over the last 20 year. 13 of those years are in Web Development. I'm currently looking into the detection of cell phones from a website, then validating speed, validating if streaming exists, screen sizes, OS type, etc.. I've started building something that will capture this info so I can start analysing headers.. http://www.dp.bz<http://www.dp.bz/> - my test bed I've looked at things like MOBI and MobileMultimedia, which seems to be where I'm going. But rather not pay for something, I think I can build myself pretty easily. For starters, I just want to figure out if someone comes to my site, if I can stream them videos or not. If they can stream then based on speed what type of video and what bit rate.. Any pointers would be greatly appreciated. -- Gavin -- Gavin
Received on Tuesday, 14 July 2009 10:30:57 UTC