You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@senssoft.apache.org by "Clay Gimenez (JIRA)" <ji...@apache.org> on 2016/10/04 13:38:21 UTC

[jira] [Commented] (SENSSOFT-29) Determine how best to track sessions and users

    [ https://issues.apache.org/jira/browse/SENSSOFT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15545362#comment-15545362 ] 

Clay Gimenez commented on SENSSOFT-29:
--------------------------------------

Sessions:  sessionStorage provides a convenient way to do this.

Users:  localStorage could allow us to track a single endpoint (end user browser) across sessions.  It would not be perfect (user can clear/modify localStorage, etc.), but could be helpful if we clean the data.  

The open question this ticket should answer is what to put in storage as an identifier.  Techniques like browser fingerprinting are often too slow/large/fragile, but something like a unix timestamp would not be distinct enough, especially at any sort of scale.  

> Determine how best to track sessions and users
> ----------------------------------------------
>
>                 Key: SENSSOFT-29
>                 URL: https://issues.apache.org/jira/browse/SENSSOFT-29
>             Project: SensSoft
>          Issue Type: New Feature
>            Reporter: Joshua Poore
>            Assignee: Clay Gimenez
>            Priority: Minor
>             Fix For: UserALE.js 0.4
>
>
> Evaluate whether we should track users across sessions via cookies or similar methods.



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