On Sat, 2006-12-02 at 22:19 +0100, Tommy Braun wrote: > On Tue, 21 Nov 2006 08:41:47 +0100, you wrote: > > give us some feedback about your ideas! >
Your thoughts inspire me to write about this subject and to make known my lasts efforts to reach some of the goals you described. The code dates June 2005, after that I've entered some tough times that demotivated me to finish this and other goals, I've becomed a procrastinator. http://www.multitel.com.uy/eroldan/quica/quica2-20050620.tar.gz Far from being finished, the code shows (not clearly maybe) my ideas at that time about what would be the next steps quica must took: * All python * Backend and Frontend. Backend expose functions by xmlrpc. Web frontend done in cherrypy (Now I prefer the turbogears kit) * Backend expose various Protocol levels. Maybe other MTA can share high level protocol, making frontends interchangeable. * Extendable protocol, frontend and backend comunicate capabilities, central registry of protocols(me). * Cluster of MTAs aware. Cluster of storage pools aware. 'perdition' like functionality aware. * Heavy use of two phase commit protocol to avoid inconsitencies. * API and protocol unittested I don't know if someday I will continue this project. I'm open to interchange ideas with anybody that has a similar vision of what the next courier frontend must be and want to make the effort do it. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
