W3C home > Mailing lists > Public > public-mw4d@w3.org > July 2009

RE: Hello all

From: Geddam Karan Deep-KHWG64 <karan.geddam@motorola.com>
Date: Tue, 14 Jul 2009 08:29:50 +0100
Message-ID: <A2C3DF730538484689D92F55C21ED719046CD9CD@zuk35exm63.ds.mot.com>
To: "Gavin Landon" <gavin.landon@gmail.com>, <Lauri.K.Hirvonen@nokia.com>
Cc: <public-mw4d@w3.org>
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
 
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> 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-supp
ort-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] On Behalf Of ext Gavin Landon
		Sent: 10 July, 2009 00:19
		To: 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 20:17:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 14 July 2009 20:17:08 GMT