On 11/9/06, Dwayne Bailey <[EMAIL PROTECTED]> wrote: > On Wed, 2006-11-08 at 11:43 +0100, Zejn Gasper wrote: > > Thinking about future, I would like to split Pootle in more standalone > > daemons: > > - web interface, Django web application as a web translation interface > > - storage, to provide a unified way of accessing translations. Since all the > > requests go through storage daemon, there's no multithreaded environment and > > there's no locking. > > These two together is good. Having simply a storage layer would allow > Pootle's to talk to each other and also allow remote GUI editors to talk > to Pootle Server.
Now we're talking! Web services can be of good use here also. Maybe SOAP / WSDL and/or XMLRPC and/or some other custom (simplified) XML-based protocol could be really handy (the latter particularly when one creates Ajax-based translation interfaces into the future). Most development frameworks have good support for at least one of these today and it should make integration with remote clients a breeze. This will also simplify the Django-based web front-end component. And if you don't want to use the web interface then just ditch that part and just install the daemon. So basically we could have the following separate components if we wanted: 1) The storage daemon 2) The server-side XML interface(s) 3) The web-based user interface 4) The client desktop application Keep being brilliant, people, I really like where this is going. :) -- Charl van Niekerk http://charlvn.za.net ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
