-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
After giving some thought to the issue (and looking at the prev -stats implementation details), here's the proposed design for the new -stats. I'd love commoents, new ideas or what's else on your mind, so it can be taken into account upon implementation. 1. xml-rpc for communications Seperation of communication mechanism from data. This will prevent the need to track different protocols as the server/client evolve (we can add more fields to struct, unaware clients can ignore them). It's standarts based (XML over HTTP), and save the need for implementing the protocol itself (or tracking/handling/parsing GET/POST params for with the client for example). 2. client side. Rewrite with python (now in perl) Will allow us to tap into portage API if/when needed. Python already installed on all gentoo systems, and includes all the needed modules (including xml-rpc). Current perl client depends on additional perl modules (e.g: MIME-Base64, URl, HTML-Tagset and more). 3. Server side Rewrite with PHP. PHP's PEAR has a good xml-rpc implementation. Redesign and normalize the db, use prefix for tables (will ease deployment in case of a need to share db fex). Accomodate additional features (searchable package files list?). Check possiblity of interaction with the new packages.gentoo.org system (fex: getting the current package list) ? Utilize smarty for web interface (seperate code from display). 4. Delpoment machine Development will take place under my own server for now . Will be deployed on gentoo's infrastructure upon completion. Hope we can utilize a cvs module for it, allowing others to participate. Cheers - -- Meir Kriheli MKsoft systems http://www.mksoft.co.il -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/uRtURkS5DWK1mZkRApwTAJ9HqgrkjuCkWQgk9nvdSFqacoQmlACg6bZr qXSrO7eX2Y6Ii70MHTlcO9E= =i5pU -----END PGP SIGNATURE----- -- [EMAIL PROTECTED] mailing list
