Re: [silpa-discuss] [smc-discuss] Summer of Code , REST Infrastructure for Silpa-Flask

[Vasudev Kamath]

On Tue, Feb 25, 2014 at 11:05 PM, Nithin Saji <address@hidden> wrote:
> I had planned to do this last year and had  some confusion regarding the the
> "REST" part of the api. Almost all modules only offer two or three functions
> which would require only a POST request.

First to clarify what we need is sane API calls which can be easily
used let it be REST or just http api's both are perfectly fine with
us.

>  We won't need PUT,GET,DELETE for  any of the modules. So isn't it better if
> we rewrite the JSONRPC view class for a http api format instead of going for
> a full fledged RESTful extension whose features we won't use anyway but ends
> up  adding more dependencies  and extra cruft to the codebase ?

First we are not facing out JSONRPC we just can't because it is used
by some people.

>
> Also if I am guessing, all routing rules should reside within silpa-flask
> app and you will have to go for a  consistent api for all modules like
> `.../api/module/method` and rest of the request as post data. You should be
> able to impliment this with a rewrite of JSONRPC module and  the routing for
> it.

Why would each module needs to be changed? JSONRPC is only specific to
framework and modules are not convoluted with unrelated code,
similarly I'm pretty sure its completely possible to do the same for
REST i.e. keep the code related to rest only in framework.

To say at one point of time all modules were strongly tied to silpa
framework, we did manage to separate it out didn't we?


-- 

Vasudev Kamath
http://copyninja.info
address@hidden|vasudev.homelinux.net}