Last post Aug 03, 2006 05:03 PM by mpwizard
Nov 28, 2003 10:58 PM|vpikula|LINK
Dec 05, 2003 02:23 AM|kashif|LINK
Dec 09, 2003 06:44 AM|vpikula|LINK
Jan 09, 2004 08:58 PM|rakeshg|LINK
Mar 11, 2004 06:14 AM|gordon1509|LINK
Mar 16, 2004 07:41 AM|Qnnn|LINK
Mar 17, 2004 10:47 AM|masondx|LINK
Mar 17, 2004 11:31 AM|Qnnn|LINK
Apr 06, 2004 05:21 AM|gordon1509|LINK
Apr 06, 2004 06:04 AM|Qnnn|LINK
Apr 06, 2004 02:51 PM|follesoe|LINK
Apr 07, 2004 05:26 AM|gordon1509|LINK
Apr 12, 2004 04:52 PM|Qnnn|LINK
Apr 15, 2004 02:02 PM|follesoe|LINK
Apr 16, 2004 02:10 AM|Qnnn|LINK
Apr 16, 2004 04:51 AM|follesoe|LINK
May 24, 2006 07:25 PM|bluekiwi|LINK
The plan is that each device is going to ship a url to a device .xml file along with it's user agent string. that way the runtime could read the values from a central resposatory automaticly.
Jun 01, 2006 12:55 PM|mpwizard|LINK
Devices to send out a link to a UAProfile in their headers now, at least.
You can visit this URL for profiles... we've got a lot more features almost here for the real-time repository stuff, but this site is where we started.
Jun 02, 2006 05:10 AM|bluekiwi|LINK
Jun 05, 2006 06:07 AM|mpwizard|LINK
We've developed a web service that would enable .NET programmers to do just that which is launching soon-ish. It returns an XML containing an array of keys and an array of values which are then combined, since the returned device profile contains different
things depending on how much data is in the database, how much customer-specific data can be extracted from the headers, that kind of thing.
The fact that there are now 2799 UAProfiles on our site kind of points to the difficulty of keeping a web.config file up to date. The current approach is brave but unwieldy when you get into the mobile sphere.
Jun 06, 2006 01:53 PM|bluekiwi|LINK
Jun 09, 2006 05:08 AM|mpwizard|LINK
When it's launched I'll point to the WSDL and downloadable client software, and how to get a test account... however, the whole thing kind of bypasses the CLR: you wouldn't need to use the browser config stuff to use the service: this is partly because the
web service is a fair bit more intelligent than the CLR and gives you more properties. Plus it analyses agent strings it hasn't seen before intelligently and is zero maintenance. That's as well as the geolocation information, etc.
The result returned from the web service is an array of keys and an array of values which are then put back into an array. Has to be this way because the schema is variable from device to device. I don't agree with services which return data at all costs
even if it's wrong for the sake of a full-looking schema.
Returning the XML documents as the CLR requires it is non-trivial because UAProfiles don't contain agent strings, and if you were to look at a table of agent strings and UAProfile.com URLs, you'd find that this is because there are multiple possible agent
strings to a UAProfile (growing all the time, too, as new firmware is released). That would mean that a UAProfile would return either many different CLRs (if no human was pressed into service to produce a RegExp), or a human would have to get involved in creating
the CLRs manually by crosschecking each UAP and creating a RegExp for each one.
Unless someone has a nice little routine that takes multiple strings and works out a regexp to describe all of them? Then the problem would be reduced to relatively trivial.
Jun 09, 2006 05:53 AM|bluekiwi|LINK
Aug 03, 2006 05:03 PM|mpwizard|LINK
If you join http://www.uaprofile.com you automatically get a free evaluation/developer licence for the system: and you can download the .NET .VB file (check the "DetectRight" link).
I'd appreciate feedback on that, actually, of the "oh noes!" variety,or the "why did you do it this way? Much better to do it this day" kind of thing. I'm an experienced programmer, but .NET has the habit of making you regularly feel like a newbie all over
Oh yes, because our system is Linux-based (sorry, .NET heads!), it demands you allow "unsafe" header parsing (if I could persuade Apache to do it right, I would!).
Anyway, http://www.uaprofile.com is the place to start. We're still seriously looking at doing something with the browser.config format with DetectRight.