Also, at weather, we actually did find good value in exposing an OpenDDR json service to our sites to help identify browsers, tablets, and phones and other DDR metrics which aren't easily attainable in js. So I'm thinking this might be a good first step when the new DDR is available, exposing a public service?
--- Sent from Blackberry Bold 9900 ----- Original Message ----- From: Naghibi, Reza [mailto:[email protected]] Sent: Friday, December 21, 2012 11:37 AM To: '[email protected]' <[email protected]> Subject: Re: User-Agent classification So it sounds like for classification: -ability to classify a UA in real time to be used in some kind of routing, access, or presentation decision -ability to classify a UA after the fact to be used for metrics and/or analysis As for the DDR, it sounds like there is a need to support getting a configurable DDR from a database? I think this is a good idea as well. Am I missing anything else here? --- Sent from Blackberry Bold 9900 From: Werner Keil [mailto:[email protected]] Sent: Friday, December 21, 2012 07:50 AM To: [email protected] <[email protected]> Subject: Re: User-Agent classification Bertand/all, Thanks a lot for continuing this discussion here. While it shouldn't be limited to one data store as I briefly discussed with Eberhard in an earlier thread (recommending, we continue it here now[cid:[email protected]]) there are several projects and options even inside the Apache universe. Cassandra being just one to mention. Maybe that new Wiki or JIRA could also provide further points to gather this and other ideas to design and improve DeviceMap. Werner On Fri, Dec 21, 2012 at 9:54 AM, Bertrand Delacretaz <[email protected]<mailto:[email protected]>> wrote: Hi, On Fri, Dec 21, 2012 at 8:48 AM, eberhard speer jr. <[email protected]<mailto:[email protected]>> wrote: > ...My fork of the OpenDDR code -- Miri (http://www.ducis.net/miri) -- > only differs from the origial OpenDDR in that it can connect to > various different data-sources... Interesting - IMO DeviceMap should do the same, allow people to plugin their own data sources. > ...It seems to me that a good versatile DDR should also be useable for > traffic analyses (how many Android vs. iOS requests were there, is > Fennec 'popular', what's MS's newfangled devices' share, etc)... Why not - this goes beyond my own needs right now, but it's probably a good idea to make things sufficiently modular to enable those kinds of use cases. >... Another area of functionality I see is : connecting to the 'user'. > All solutions fail miserably to connect to their actual intended > audience : website makers and operators. > I think there are two areas here : implementing a DDR solution, i.e. : > inserting routing 'forks' in running sites to route traffic to the > appropriate content, and secondly : building content with specific > groups of devices in mind.... I'm not sure if that's within scope for DeviceMap, but again keeping things modular so that such things are doable, maybe with some assembly, is a good idea. > > Returning to the 'database' +65,000 of user-agents I can contribute... If you're ready to contribute that data to DeviceMap, feel free to create a jira issue, and if you can provide patches to use that that data with the current code all the better. -Bertrand
