Changes between Version 18 and Version 19 of BluePrint/Synchronisation


Ignore:
Timestamp:
05/08/09 09:08:12 (13 years ago)
Author:
Fran Boon
Comment:

Don't attempt to hyperlink unless desired

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/Synchronisation

    v18 v19  
    11= Blueprint for Synchronization =
    22
    3 We need to implement a system performing automatic Sahana synchronization. This Synchronization will be between any Sahana servers (PHP and Py). Our focus should be on ShanaPy but it should be compatible with SahanaPHP.
    4 Currently SahanaPy data exporting module exports data in CSV (web based: not for autonomous process). We can add support for XML and JSON.
     3We need to implement a system performing automatic Sahana synchronization. This Synchronization will be between any Sahana servers (PHP and Py). Our focus should be on !SahanaPy but it should be compatible with SahanaPHP.
     4Currently !SahanaPy data exporting module exports data in CSV (web based: not for autonomous process). We can add support for XML and JSON.
    55XML exporting will insure compatibility with PHP version Sahana. JSON is modern, futuristic, light over HTTP and reliable, so using JSON for data synchronization looks promising. These should strictly adhere to XSD standards set approved by W3C.
    66
    7 Another important point is to use UUID information of each of sync activity. We must include UUID while exporting data. Current UUID of export module of PHP version includes 'Instance ID' to make it clear which install instance it belongs to. Similar approach should also be adopted in SahanaPy.
     7Another important point is to use UUID information of each of sync activity. We must include UUID while exporting data. Current UUID of export module of PHP version includes 'Instance ID' to make it clear which install instance it belongs to. Similar approach should also be adopted in !SahanaPy.
    88
    99Automatic synchronization is different from manual data export / import module present in Sahana. Automatic process should run continuously as daemon.
     
    3131For this to work with PHP version, we MUST make port this software with PHP version and we MUST must expose web services in PHP version for doing sync. We must find someone in PHP developers who can do it.
    3232
    33 We can always ship this with PortablePython eliminating need of installing Python on end machines (like what XAMPP is doing for PHP and MySQL)
     33We can always ship this with !PortablePython eliminating need of installing Python on end machines (like what XAMPP is doing for PHP and MySQL)
    3434 
    3535Reference: