Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The session data only contains the values stored in the <code>session[]</code>-hash from the user. It doesn't store which action/controller was called, so you don't know which "link was clicked".</p> <h3>Get the activity of your users:</h3> <p>Besides rackamole you have two options IMHO.</p> <ul> <li><p>Use a <code>before_filter</code> in your <code>ApplicationController</code> to store the relevant info you are interested in. (Name of controller, action or URI, additional parameters and id of the logged in user for example).</p></li> <li><p>Use an AJAX-call at the bottom of each page which posts back the info you are interested in (URI, id of logged in user, etc.) to your server. This allows faster response times from the server, as the info is stored after the page has already been delivered. Plus, you don't have to use a Rails-request to store it. The AJAX-request could also be calling a simple PHP-script writing the data to disk. This is much faster.</p></li> </ul> <h3>Storing this activity:</h3> <p>Store this data/info either in the database or in a logfile. The database will give your more flexibility like showing all actions from one user, or all visitors for one page, etc. The logfile solution will give you better performance.</p> <h3>Realtime vs. Oldschool:</h3> <p>As for pulling out your collected data in realtime, you have to build your own solution. To do this elegantly (without querying your server once a second to look if new data has arrived) you'll need another server process. <a href="https://stackoverflow.com/questions/tagged/ajax+push">Search for AJAX Push</a> for more info.</p> <p>Depending on your application I'd ask myself if realtime notifications for this are really necessary (because of all the hassles of setting this up).</p> <p>To monitor the activity on your site, it should be enough to have a page listing the latest actions and manually refresh it (or refresh it automatically every ten seconds).</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload