un-contrib-ifying the proxy

[faassen]

I'm interested in the proxy code, and I'm kind of bothered by that it's sitting in contrib. Could we consider making it a real part of the project, i.e. something like restkit.proxy? (with a backwards compatibility import in place in restkit.contrib?)

I wrote this today to show what bothers me about 'contrib' in projects (the restkit one was the one that gave me the realization, but certainly not the first one):

http://blog.startifact.com/posts/against-contrib.html

If you don't want to move it, then I will of course deal with it being in its current location.

[benoitc]

@faassen good call... However, I am thinking rather to make it available as a full project: restkit-proxy so updates and so on wouldn't depends on restkit core. Thoughts?

[faassen]

Sure, either making it part of the core or splitting it off as a separate project would work with me!