In order for Little Software Stats to begin and end collecting data, there must be start and stop event sent through the API. By default, the start event is the first event processed and the stop event is the last event that is processed.

Start

The start event includes information about the users computer, the application being used, and also a MD5 hash that is unique to that user. The unique user ID is usually generated using a MD5 hash of the users machine name, MAC address, and hard drive serial number (this information is double-encrypted so its virtually impossible to reverse the hash). Where this information is unavailable then it is recommended to have a randomly generated MD5 hash stored locally on the computer for future use. Below is a list of all the parameters that are passed with the start event:

Parameter Meaning Type Notes
tp Event Type String strApp
aid Application ID String
aver Application Version String
ID Unique User ID String
ss Session ID String See Additional Parameters
ts Timestamp Integer See Additional Parameters
osv Operating System Version String
ossp Operating System Service Pack Integer If no service pack is installed, then the value is 0
osar Operating System Architecture Integer 32 or 64
osjv Java Version String
osnet .NET Framework Version String
osnsp .NET Framework Service Pack Integer If no service pack is installed, then the value is 0
oslng Operating System Language Integer Uses LCID as specified here
osscn Screen Resolution String Must be in format [width]x[height]
cnm CPU Name String
cbr CPU Brand String Can be vendor ID or manufacturer (ie: “GenuineIntel” or “Intel”)
cfr CPU Frequency Integer Must be in MHz
ccr CPU Cores Integer
car CPU Architecture Integer 32 or 64
mtt Total RAM Integer Must be in MB
mfr Free RAM Integer Must be in MB
dtt Disk Space Total Integer Must be in MB
dfr Disk Space Free Integer Must be in MB

Other information that is stored and not specified via a parameter is the users IPv4 address and country. The country is determined using the users IPv4 address and either the MaxMind GeoLite database or GeoIPs API service. The MaxMind GeoLite database is updated about once a month and a notification will appear in the interface when an update is available.

XML Example:

<Event>
<tp>strApp</tp>
<aid>463f37d98c8219a9906b6d579311fb07</aid>
<aver>1.0</aver>
<ID>BC72D802A0340B3DF7B664D233011B28</ID>
<ss>3FAB840C61C6E2B07E369F38D287CDE5</ss>
<ts>1358746946</ts>
<osv>Windows 7</osv>
<ossp>1</ossp>
<osar>64</osar>
<osjv>1.8</osjv>
<osnet>4.0</osnet>
<osnsp>0</osnsp>
<oslng>1033</oslng>
<osscn>1024x768</osscn>
<cnm>IntelCorei7CPU950@3.07GHz</cnm>
<cbr>genuineintel</cbr>
<cfr>3076</cfr>
<ccr>8</ccr>
<car>64</car>
<mtt>6144</mtt>
<mfr>512</mfr>
<dtt>1048576</dtt>
<dfr>1024</dfr>
</Event>

Stop

The stop event is sent to tell the API that no more information is being sent. Unlike the start event, very few parameters need to be sent with the stop event. By the default, the stop event will always be the last event to be processed by the API. Below is a list of all the parameters that are passed with the stop event:

Parameter Meaning Type Notes
tp Event Type String stApp
ss Session ID String See Additional Parameters
ts Timestamp Integer See Additional Parameters

XML Example:

<Event>
<tp>stApp</tp>
<ts>1358749014</ts>
<ss>3FAB840C61C6E2B07E369F38D287CDE5</ss>
</Event>

Comments