All right. Thank for your reply. The thing I love about django is that is compactness. You simply do need no other libraries when you build web app. As opposite from java where you must use hundred of frameworks to build up a web app. My idea was to integrate a stuff needed for RPC into django to avoid usage of another lib... nothing more...
On Dec 9 2011, 8:55 am, Russell Keith-Magee <russ...@keith-magee.com> wrote: > On Thu, Dec 8, 2011 at 4:58 PM, Vaclav Klecanda <venca...@gmail.com> wrote: > > I have started with pyjamas that use JSON RPC and would like to use > > "JSON RPC views" but found only external libraries solution. I have > > written following snippets and wonder if they could be added to > > django.utils: > > Hi Vaclav, > > Thanks for the suggestion. > > The question I have for you is "Why"? > > django.utils is set of utilities that are used by the core -- it > defines the basic data structures, conversion tools, and so on that > the core of Django uses. The closest you'd get to an analog of this > sort of functionality is the feed generator, and even then -- that's > only the factory functions for generating Atom/RSS content. The actual > functionality behind syndication views is held in contrib. > > This then leads to the suggestion to put this in contrib -- to which, > again, I'm forced to ask Why? JSON-RPC is one of many RPC formats, and > as you note, there are already external libraries that implement > JSON-RPC for Django. What is gained by adding one particular JSON-RPC > solution to Django's trunk? > > Adding a particular JSON-RPC library to django.contrib won't improve > the functionality or the availability of JSON-RPC, and it won't speed > up the development of any library that is chosen for inclusion (if > anything, it will *impede* progress, because developments in the > JSON-RPC library need to be locked to the Django release cycle. > > As a broad direction, the core team is trying to minimize, and if > possible, reduce the amount of stuff in contrib. If you want to make > an argument for adding something new to contrib, you're going to need > to prove that: > > 1) There is a clearly defined problem that needs to be solved > > 2) There is broad demand for a solution to that problem > > 3) That the solution you're proposing is the best possible solution > to this problem. > > 4) Adding your solution to trunk is the best option for the community > in the long term. > > Yours, > Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
