In my opinion the biggest issue with Python RPC is that so far nobody undertook the (rather limited) effort of creating a corresponding contribution in qooxdoo-contrib, for whatever reasons. Doing so would both improve visibility to the community (so people use it) and the chances of multiple people maintaining the code (so we could have a common effort to create a good and usable Python backend; the corresponding Php solution shines in that regard).
But as things are, now three different implementations surface, by different people, in different repositories, and at different levels of currentness and completeness. I don't care if a contrib is called RpcPython or RpcPythonCherrypy or something else, as long as it gets in. But of course the original authors have to make the first step. Just my 2 cent. Thomas Andreas Ecker wrote: > Howdy! > > On Wed, 2009-06-24 at 07:53 +0200, Jacques Bousseau wrote: > >> See this project : >> http://en.letras.ru/2009/01/qooxdoo-controller-for-cherrypy >> >> Jacques >> >> Delaney Gillilan a écrit : >> >>> I noticed there is no is no official Python server so I made an >>> initial stab at creating one using the awesome and fast http >>> cherrypy server (www.cherrypy.org). Created with svn trunk of >>> cherrypy but 3.1 should work as well. Obviously my tests need work >>> but I implemented everything on >>> http://qooxdoo.org/documentation/0.8/rpc_server_writer_guide. Made >>> a bitbucket project for it at >>> http://bitbucket.org/delaney/cooks_do_cherry_pie/. Any comments or >>> thoughts for this are welcomed. >>> > > Seems there is quite some effort to implement Python RPC solutions for > qooxdoo. Besides the two approaches mentioned here there is the > original, "official" implementation by Viktor Ferenczi, see > http://qooxdoo.org/documentation/0.8/rpc_python > > I'd like to have Viktor on board as the creator of the original > qooxdoo/Python RPC solution, as he's always had many ideas to improve > the current solution but lacking time/resources. Also Thomas (at least > as an observer/supporter) as he's maintaining and advancing the > Python-based qooxdoo tool chain. > > It would be great the qooxdoo/Python devs would enjoy to collaborate in > providing an up-to-date RPC solution. This could also ensure the project > kept being actively maintained and not going stale. Is there more than > one environment to target (e.g. built around Cherry.py or not), which > would mean more than on project? > > Let's see what the technical discussion leads to (for now I'd suggest to > use the mailinglist for discussion, not a dedicated enhancement request > in bugzilla). Whatever the proposals might be, I can well envision to > start to host and incubate at least one such project as a contribution > in qooxdoo-contrib. > > qooxdoo/Python people speak up! ;-) > > Andreas > > -- Thomas Herchenröder Development Technology & Architecture - Web Technologies 1&1 Internet AG phone: +49 (0)721 91374-4482 Ernst-Frey-Str.9 web : www.1und1.de 76135 Karlsruhe qooxdoo.org Amtsgericht Montabaur HRB 6484 Vorstand: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas Gottschlich, Robert Hoffmann, Markus Huhn, Hans-Henning Kettler, Dr. Oliver Mauss, Jan Oetjen Aufsichtsratsvorsitzender: Michael Scheeren ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
