[Pidgin] GSoC2012/Statscollector modified

Pidgin trac at pidgin.im
Sat Aug 18 11:13:58 EDT 2012


Changed page "GSoC2012/Statscollector" by sanket from 180.151.40.138*
Page URL: <http://developer.pidgin.im/wiki/GSoC2012/Statscollector>
Diff URL: <http://developer.pidgin.im/wiki/GSoC2012/Statscollector?action=diff&version=2>
Revision 2

-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: GSoC2012/Statscollector
=========================================================================
--- GSoC2012/Statscollector (version: 1)
+++ GSoC2012/Statscollector (version: 2)
@@ -47,4 +47,6 @@
 The server is basically a collator which collects all the stats.xml and transforms them into a useful database (we obviously don't want to be working on raw xml's). For the interested it's written in [http://djangoproject.com/ Django] and uses the awesome [http://highcharts.com/ Highcharts] Javascript Library. Thanks Eion, for the recommendation on the charts library :-)!
 
 === Processing Stats ===
-One major challenge for this server was to sort the XML's efficiently. Because utlimately it's going to hit a lot of traffic and rendering information should be efficient, to be short! I have followed the following workflow: on submitting stats.xml the server will breakdown the file and store it into a database schema. All queries for date ranges by users then, will be simple select * from db where date >= d1 and date <=d2 format. MySql or any RDBMS will be ideally suited for these queries. I had to make sure that Django's abstraction did not screw up the efficiency, because your logic can change the type of query you make -- without you knowi
+One major challenge for this server was to sort the XML's efficiently. Because utlimately it's going to hit a lot of traffic and rendering information should be efficient, to be short! I have followed the following workflow: on submitting stats.xml the server will breakdown the file and store it into a database schema. All queries for date ranges by users then, will be simple select * from db where date >= d1 and date <=d2 format. MySql or any RDBMS will be ideally suited for these queries. I had to make sure that Django's abstraction did not screw up the efficiency, because your logic can change the type of query you make -- without you knowing it!
+
+== Ensuring server names in prpl-jabber/irc are public ==

-------8<------8<------8<------8<------8<------8<------8<------8<--------

* The IP shown here might not mean anything if the user or the server is
behind a proxy.

--
Pidgin <http://pidgin.im>
Pidgin

This is an automated message. Someone at http://pidgin.im added your email
address to be notified of changes on GSoC2012/Statscollector. If it was not you, please
report to .


More information about the Wikiedit mailing list