Poll: REST support?
You do not have permission to vote in this poll.
yes
84.52%
71 84.52%
no
9.52%
8 9.52%
maybe
5.95%
5 5.95%
Total 84 vote(s) 100%
* You voted for this item. [Show Results]

  • 2 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
REST support

#1
Should CI4 provide built-in support for RESTful services?
This would imply handling data format translations (JSON, XML, text...) as well as providing a base REST_Controller to extend in an app.

--------------------------------
Disclaimer: Putting forward an idea without implying any endorsement of it.
James Parry
Project Lead
Reply

#2
Those days REST is a must as its common used api solution by many systems.

Just I am not sure if REST_Controller is a good idea.
Perhaps Trait or Interface will be better solution than making different type of controllers..
Best VPS Hosting : Digital Ocean
Reply

#3
Yes, REST is required, but REST_Controller is not.

How about a core Formatter? It can serialize the input in Input and deserialize the output in Output by the specified Content-Type.
Reply

#4
Yes, REST is required, but REST_Controller is not.
Reply

#5
(04-12-2015, 04:34 PM)jiang.tao Wrote: Yes, REST is required, but REST_Controller is not.

How about a core Formatter? It can serialize the input in Input and deserialize the output in Output by the specified Content-Type.

Sounds like Formatter should be a separate CI4 thread??
Reply

#6
I think setting up the routing for REST should be easier than it currently is, and that formatting options should be available for different response types. However, I don't think it's necessary for either of these to be tied to the controller, nor is it necessary to implement both.

I think 3rd party routing solutions are currently more commonly available than response types/output formatters. I also think it will take some careful planning to implement response types/output formatters in a manner which will be useful to a wide developer base and easily extended.
Reply

#7
(04-12-2015, 07:13 PM)cjj Wrote: Yes, REST is required, but REST_Controller is not.

I think so too.
Reply

#8
I think that rest will be hard with the current db models which we have ..
It requires orm base objects matching table scheme and auto validation which is not as form validating.

If we want such suppport in ci 4 we need and new model types, and perhaps validation must not be form validation but a validation..

Just thoughts. ..
Best VPS Hosting : Digital Ocean
Reply

#9
(04-15-2015, 01:01 AM)sv3tli0 Wrote: I think that rest will be hard with the current db models which we have ..
It requires orm base objects matching table scheme and auto validation which is not as form validating.

If we want such suppport in ci 4 we need and new model types, and perhaps validation must not be form validation but a validation..

Just thoughts. ..

Hmmm - I thought REST addressed the usage of HTTP methods, and the automatic translation of data formats.
I don't recall anything suggesting an ORM or auto validation.

Those might be good ideas on their own, but I see nothing to prevent REST from working with the current CI Model.
Reply

#10
Yes but it will be pointless to make anything more than an Interface and a rest router definition as all methods has to be covered 1 by 1 by devs.

How ever I already am not sure that anything from those things should be directly at the framework..

May be we have to think for CI extension support and half of the ci4 ideas to be extensions instead of build in features
Best VPS Hosting : Digital Ocean
Reply


Digg   Delicious   Reddit   Facebook   Twitter   StumbleUpon  


  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2021 MyBB Group.