JSON Schema suggestions about statistics

[abdullahc]

Hi,

This is Google query example:

https___encrypted_google_com/#hl=en&cp=4&gs_id=g&xhr=t&q=test&tok=rKERIj9CmPJYLt2xn-JFsQ&pf=p&sclient=psy&site=&source=hp&pbx=1&oq=test&aq=0&aqi=g5&aql=&gs_sm=&gs_upl=&bav=on.2,or.r_gc.r_pw.&fp=8aeaac4c950b243c&biw=1280&bih=664

It collects many additional data for statistics about its client. I would suggest the same thing even if the stats module is not implemented. Users should be aware of.

Example of the fields I think it's better to see:

programming language: php, python...
client_type: website (no direct connection with user), direct_end_user, indirect_end_user (js & html modules in other sites), desktop gui,cli, or lib
application/site name:
os:
cms for modules:

I will cool if we could get end_user info with website (php,..., site in middle ) info

[Assem Chelli (عاصم شلي) (assem-ch)]

Hi,

yes, i think its important .it needs a deep study if we want to use an ID and a secret key for trusted applications.

to send these information with every query is not fair, may be the connection to the service must be synchronized .

[abdullahc (sneetsher)]

Yeah,

Information may sent once, then the client got a rundom/hash client_id/or token within schema. then the client will continue sending just that token, but it will remain (optional).