You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@devicemap.apache.org by "Volkan Yazıcı (JIRA)" <ji...@apache.org> on 2017/01/02 13:39:58 UTC

[jira] [Updated] (DMAP-204) Mention about DeviceMap successor YAUAA

     [ https://issues.apache.org/jira/browse/DMAP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Volkan Yazıcı updated DMAP-204:
-------------------------------
    Summary: Mention about DeviceMap successor YAUAA  (was: Mention about DeviceMap successor)

> Mention about DeviceMap successor YAUAA
> ---------------------------------------
>
>                 Key: DMAP-204
>                 URL: https://issues.apache.org/jira/browse/DMAP-204
>             Project: DeviceMap
>          Issue Type: Bug
>            Reporter: Volkan Yazıcı
>            Assignee: Radu Cotescu
>
> After the move of DeviceMap to attic, it is wise to mention about the potential alternatives/successors for the records. As has been [discussed in the Device Map mailing list|http://mail-archives.apache.org/mod_mbox/devicemap-dev/201612.mbox/browser], [YAUAA|https://github.com/nielsbasjes/yauaa/] stands as a viable alternative. Would you mind putting the following text to the [http://attic.apache.org/projects/devicemap.html]:
> Future references can point to [YAUAA: Yet Another UserAgent Analyzer|https://github.com/nielsbasjes/yauaa/] as a viable alternative. Rather than employing a fixed collection of User-Agent (UA) strings as in DeviceMap, YAUAA performs a semantic analysis to determine certain attributes of the UA.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)