Comments on: Improving Django: Generic views for RESTful web services

By: Uqupodee

Uqupodee — Sun, 25 Sep 2011 09:22:31 +0000

I'm not sure Tube Top Models 09902

By: Tfwykwyu

Tfwykwyu — Tue, 06 Sep 2011 20:50:24 +0000

Photography lolita teen 8-(((

By: Rszikcee

Rszikcee — Tue, 06 Sep 2011 18:54:37 +0000

I'll put her on lolita nude 395380

By: Tabitha Jennings

Tabitha Jennings — Sat, 10 Jan 2009 19:51:00 +0000

hi
h61s8ith9f4z95r0
good luck

By: Eugene Jackson

Eugene Jackson — Fri, 09 Jan 2009 06:35:52 +0000

hi
h61s8ith9f4z95r0
good luck

By: company life insurance valley stonebridge

company life insurance valley stonebridge — Thu, 08 Jan 2009 22:37:55 +0000

company stonebridge plano life insurance insurance life plano company stonebridge

By: Bookmarks about App

Bookmarks about App — Sat, 04 Oct 2008 08:15:13 +0000

[...] – bookmarked by 1 members originally found by Roncip on 2008-09-16 Improving Django: Generic views for RESTful web services http://www.aiplayground.org/artikel/improving-django/ – bookmarked by 5 members originally found [...]

By: Thorben

Thorben — Thu, 22 Nov 2007 01:24:12 +0000

Vielleicht solltest du doch “Captchas” einbauen :-)

By: stone mind » Another django-restful-model-views Update.

stone mind » Another django-restful-model-views Update. — Fri, 27 Apr 2007 13:34:40 +0000

[...] I mentioned a few weeks ago, Andreas Stuhlmueller has proposed a general REST API for Django, and as his ideas and mine seemed very compatible, we began talking about collaborating on a joint [...]

By: adam smith

adam smith — Tue, 17 Apr 2007 14:12:00 +0000

Hello again and sorry for the late response, I’ve been busier than usual with freelance work, and I just got around to checking your site again.

I’m glad you’re open to collaborating! I think together we will come up with very robust solution. Have you given thought as to how you want to proceed?

(Incidentally, I think your English is excellent–better than many native speakers I know… but don’t hesitate to let me know if I am ever unclear.)

Here are a few preliminary thoughts I have. Your blog post prompted me to make a few quick updates to my existing code to factor out the model specific approach more, so that its now ready (I think) to allow developers to define resources that are not directly tied to models. If you like the basic approach I took, we could use this as a starting point, just let me know if there are areas that you would like clarified, or if there are areas you think should be cleaned up more. I also believe that nothing is set in stone and would be prepared to start from scratch also if that makes the most sense.

Either way, we should probably start a new project site and deprecate the one I started. The Google project hosting seems to be easier to use than Source Forge, but I suspect that you can’t just rename an existing project. Do you have a preference?

My knowledge of Ruby on Rails comes purely as a spectator–I haven’t used it yet myself, although that might happen as part of ongoing research into the ideas they’ve come up with. And as I said, because I am also new to the REST philosophy, and still very new to Django, and because you seem to be more experienced with Django at least, I would be happy to follow your lead on this project. Besides, my best ideas may already be in the existing code, while I think you have a strong vision for how to take it to the next level and beyond.

Also, I have a significant project in the works for which I am planning to use Django, and I could use the developing REST API underneath so we would have that as an extra reality check.

Let me know your thoughts on this. I think I am ready to proceed, even if its slowly at first. I’m really excited about the possibilities here.

Feel free to contact me directly at my email address below.

adam smith
ajs17@cornell.edu