Jean-Baptiste BRIAUD -- Novlog wrote: > > >> 1) Implementation >> >> If you look through the individual implementations, they have quite >> different ways of actually invoking the service methods. This is due to >> language specificities and to the different ways the servers work (Script >> vs. standalone server vs. servlet container). However, I think some >> effort >> could be made to offer a more uniform way of implementation which allows >> users to switch backends more easily. This also touches some points Burak >> has recently made concerning his SOAP backend. > > I do not agree. This will ends up with bad implementation in all language > in a desperate and impossible try to make all implementation the same > regardless of the languages differences. > I'm afraid it is just normal that implem differs. > API and protocols should be strictly shared to allow to switch > implementation. > >
Since you're also making this point, I want to make myself clear: I did not mean to force a paradigm on all implementations regardless of language. What I meant was implementing a common set of behaviors - for example, introspection comes to my mind, or security - or ways of designing the API, the documentation , the method signature, etc., all things that can be implemented one was or another regardless of language. I think there are allways at least two ways things can be implemented in a language "naturally", and I would think it was better for users if they are similar across implementations. But this is certainly not a No. 1 priority - just a "would-be-nice" thing to keep in mind. Jean-Baptiste BRIAUD -- Novlog wrote: > > Do you mean currently, it is not possible to simply switched from a PHP > backend to a Java backend using RPC-PHP and then RPC-Java ? > It is as simple or as difficult as the developer's skills, I guess ;-) - My point concerned more the way a new user would look at the backends and say: "Ok, for this particular task, this backend is more suited than the others", and some conceptual similarity certainly helps in deciding this question. But as I said, the streamlining of implementations is certainly not the key issue here. C. -- View this message in context: http://n2.nabble.com/Rpc-backend-harmonization-tp4075821p4076039.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
