Re: GSoC - Generic REST API module for Django

Malcolm, I'm just following up on my last post. I have gone over the django- restapi library and would appreciate more guidance on the intended direction of the project. As you suggested, following up on the existing work there is a great way to get this feature to the public this summer.

Re: GSoC - Generic REST API module for Django

Malcom, I took a look at django-restapi and it seems like a great start. Having been the mentor for the first run at it, what features would you like to see added? If you have a minute, I think that would definitely serve as a great guide. Thanks, Bill Konrad On Mar 31, 9:15 pm, Malcolm

Re: GSoC - Generic REST API module for Django

On Tue, 2009-03-31 at 17:31 -0700, Bill Konrad wrote: > First off, thanks for taking the time to read through it and give so > much feedback. > > Please let me clarify one thing. If you read the above as a proposal > than it wouldn't have seemed much like a proposal. I was only > outlining

Re: GSoC - Generic REST API module for Django

For the record, here is a list of somewhat related projects: http://opensource.washingtontimes.com/projects/django-apibuilder/ http://github.com/ingenieroariel/dapi/ http://code.google.com/p/django-restapi/ http://github.com/fiam/wapi/

Re: GSoC - Generic REST API module for Django

First off, thanks for taking the time to read through it and give so much feedback. Please let me clarify one thing. If you read the above as a proposal than it wouldn't have seemed much like a proposal. I was only outlining what a REST API module (I know you don't like that naming) would need

Re: GSoC - Generic REST API module for Django

On Tue, 2009-03-31 at 15:36 -0700, Bill Konrad wrote: > Ivan, > > Thanks for the quick feedback. What I meant by predictable (and maybe > it's the wrong word in this case) is that when assigning a URI to a > resource, a convention is followed, not that the user can "predict" > the URI itself.

Re: GSoC - Generic REST API module for Django

On Tue, 2009-03-31 at 14:35 -0700, bkonrad wrote: > I was fortunate enough today to have a quick chat with Jacob Kaplan- > Moss about the concept of a generic REST API module for Django. We > spoke about how this has been attempted before and some of the > remaining issues that still require

Re: GSoC - Generic REST API module for Django

On Tue, Mar 31, 2009 at 6:38 PM, Bill Konrad wrote: > > Kaylan, > > Good point. That would have to be a part of the specification 100%. > Any foreign key table entries that are "folded in" would have to check > out with the permissions component. > > On Mar 31, 6:24 pm,

Re: GSoC - Generic REST API module for Django

Kaylan, Good point. That would have to be a part of the specification 100%. Any foreign key table entries that are "folded in" would have to check out with the permissions component. On Mar 31, 6:24 pm, Kalyan Lanka wrote: > I am not a Django developer but have

Re: GSoC - Generic REST API module for Django

Ivan, Thanks for the quick feedback. What I meant by predictable (and maybe it's the wrong word in this case) is that when assigning a URI to a resource, a convention is followed, not that the user can "predict" the URI itself. On Mar 31, 6:18 pm, Ivan Sagalaev

Re: GSoC - Generic REST API module for Django

I am not a Django developer but have been closely following this group as I have been in love with Django framework since I started using it. You guys have done a great job. > > > 6. Proper Links / Foreign Key Resources > > If the request for primary key starts our sending out "foldable"

Re: GSoC - Generic REST API module for Django

bkonrad wrote: > 1.Predictable URI Naming Apart from my serious doubt that this can be done at all I'd like to point out that the very notion of *predicting* URLs is not RESTful. URLs are generated by server (by whatever logic it chooses) and client treats them as opaque identifiers. The

GSoC - Generic REST API module for Django

I was fortunate enough today to have a quick chat with Jacob Kaplan- Moss about the concept of a generic REST API module for Django. We spoke about how this has been attempted before and some of the remaining issues that still require attention. After our chat, I compiled a problem statement