It has a better pattern matching algorithm than the donated OpenDDR client which is more accurate and much faster.
________________________________ From: Werner Keil <[email protected]> To: "[email protected]" <[email protected]>; Reza <[email protected]> Sent: Sunday, March 23, 2014 5:27 PM Subject: Re: ;-) If e.g. it performs much better than the W3C DDR Equivalent or offers further details, no worries, I am not saying it must be. However, I can only show and offer the Java (EE) Community what we have at the moment, maybe some of them would like to help with the other Client. I will mention all these in my slides, images or benchmarks, including between Simple DDR and the other Client (only Java please, no .NET or JavaScript here) or between DeviceMap and other options like WURFL are welcome. So far I got memory footprint, see the OpenDDR slides from 2011: http://de.slideshare.net/keilw/openddr (so far except UOMo the single most viewed presentation I got on SlideShare btw. Werner On Sun, Mar 23, 2014 at 10:05 PM, Reza <[email protected]> wrote: There is no webapp example right now that I am aware of. No W3C DDR support at this time, wouldnt be hard to wrap a W3C DDR layer around the API, but thats a todo. > > > >________________________________ > From: Werner Keil <[email protected]> >To: "[email protected]" <[email protected]>; >Reza <[email protected]> >Sent: Sunday, March 23, 2014 4:36 PM >Subject: Re: ;-) > > > > >Unfortunately that one doesn't implement W3C DDR any more, and worse, there >is no working example WebApp. > >Or can you point to one, please? > > > >On Sun, Mar 23, 2014 at 9:32 PM, Reza <[email protected]> wrote: > >This implementation: >> >>https://svn.apache.org/repos/asf/incubator/devicemap/trunk/devicemap/java/src/main/java/org/apache/devicemap/client/ >> >> >> >>Its the total rewrite I did last year for DeviceMap. The rewrite simplified >>the API greatly and also increased the accuracy. >> >>String test="Mozilla/5.0 (Linux; U; Android 2.2; en; HTC Aria A6380 >>Build/ERE27) AppleWebKit/540.13+ (KHTML, like Gecko) Version/3.1 Mobile >>Safari/524.15.0"; >>DeviceMapClient client=new DeviceMapClient(); >>Map<String,String> m=client.classify(test); >> >> >> >>________________________________ >> From: Werner Keil <[email protected]> >>To: "[email protected]" >><[email protected]>; Reza <[email protected]> >>Sent: Sunday, March 23, 2014 4:20 PM >>Subject: Re: ;-) >> >> >> >> >>It already does >>If you mean DDR Simple implementation. The org.openddr Dependency where it >>existed was merely a line or two, works perfectly fine with the DeviceMap >>version in our SVN >>And the latest DDR data after syncing it. >> >>Werner >> >> >>On Sun, Mar 23, 2014 at 9:09 PM, Reza <[email protected]> wrote: >> >>Ahh... there it is. Yes, thats the old OpenDDR code, I would avoid that one. >>Not accurate... >>> >>>Using the new DeviceMap java code would be really simple, like 5 lines of >>>code... >>> >>> >>>________________________________ >>> From: Werner Keil <[email protected]> >>>To: eberhard speer jr. <[email protected]>; >>>"[email protected]" <[email protected]> >>>Sent: Sunday, March 23, 2014 4:00 PM >>>Subject: Re: ;-) >>> >>> >>> >>> >>>As a matter of fact, this Web Service Example Reza contributed to DeviceMap >>>Repo: >>>https://svn.apache.org/repos/asf/incubator/devicemap/trunk/contrib/web/webservice-java >>> >>> >>>Is the one that works best since the good old OpenDDR Filter. Not surprising >>>as it also uses a similar one, but the result is somewhat better. >>>E.g. in Chrome the actual screen resolution of a desktop PC is properly >>>detected. So are most other cases, e.g. a Nexus 7 I simulated in a Chrome >>>plugin. >>> >>>I heard your examples were mostly .NET that and support for other languages >>>is welcome to outline a wider scope of DeviceMap, but for the concrete Java >>>event I won''t show other examples live than the Java ones. I was asked if I >>>want to present DeviceMap at a nearby MeetUp, in June maybe, there other >>>language bindings could be useful >>> >>>Werner >>> >>>On Sun, Mar 23, 2014 at 8:43 PM, eberhard speer jr. <[email protected]> wrote: >>> >>>-----BEGIN PGP SIGNED MESSAGE----- >>>>Hash: SHA1 >>>> >>>>Hi, >>>> >>>>no hard feelings I hope ;-) >>>>but please look that Reza's examples >>>>You will notice the examples use OpenDDR data and his [clever] dClass >>>>c-code...and *not* DeveceMap's Java code. (1) >>>> >>>>My examples use the Apache DeviceMap .Net code 'as is' available from >>>>the repository. >>>> >>>>After your email about the Nexus 7 and trying the URL and Reza's >>>>equally valid comments, I immediately updated the API and in doing so >>>>met your and 1.5 of Reza's 'requirements'/use-cases [and without any >>>>client js code etc !]...all using DeviceMap and OpenDDR. >>>> >>>>To be fair, I appear to be the only one "relevant" to DeviceMap in >>>>this ;-) >>>> >>>>esjr >>>> >>>>(1) It should be noted that the current DeviceMap code, is Reza >>>>porting his dClass code to Java which I in turn 'ported' to .Net. >>>>-----BEGIN PGP SIGNATURE----- >>>>Version: GnuPG v1.4.8 (MingW32) >>>>Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ >>>> >>>>iQEcBAEBAgAGBQJTLzl+AAoJEOxywXcFLKYcSHIIAKrSTC7TjV3lStlmqxo3I4rB >>>>VmuLHW8h4HJluoSip+iEuWboKXMVf7r1YQsPv54jMRO2ewZJ5UPPeZIkMaz8BeDt >>>>ZUpl2LhWnko5Yz/peWXs7Y34NrLhxNC0T6GosSwSZOfYXVJ58+FghCTZAvB4ZhKp >>>>q8E03SqgwSSGu11AXVMUJgf0onQ5wDJk+qHmlWa+Agawzw23sE2XmeKjmit+suKD >>>>bjLP9UUJIfXFD0JFDSOKSpkeGd7WkyDA4QfybHEZgY782+K/G3wrGTpGKEyfxpap >>>>b/FlZYK29GveP7wXVfmqo+YMwpey19W4hSJ6ctkWy7Pz7U/TDNG19hIN/oxvags= >>>>=KNpA >>>>-----END PGP SIGNATURE----- >>>>
