Last post Mar 15, 2012 02:15 AM by zhangbenrong
Mar 09, 2012 02:29 AM|InterTed|LINK
Been playing around with SPA and the new WebAPI combined with Upshot.js. This all looks very promising!
But it seems like the Upshot.js bits do not conform to the RESTful communication standards, e.g. using RESTful urls and Restful HTTP commands and result codes.
Am I missing something here? Or is this not yet supported during beta?
Mar 09, 2012 11:22 AM|ColinBlair|LINK
For the DataController, I doubt there is any plan to make it fully RESTful the way you are asking. The DataController is not meant to compete with WCF Data Services as a fully RESTful way to interact with data.
Mar 12, 2012 05:14 AM|InterTed|LINK
The info published on http://www.asp.net/web-api/overview/web-api-routing-and-actions/creating-a-web-api-that-supports-crud-operations does suggest that the MVC Web API supports RESTful CRUD implementations.
Question is, will Upshot.js support these API implementations for SPA CRUD client operations?
Mar 12, 2012 12:52 PM|ColinBlair|LINK
Upshot.js with the correct DataProvider, yes. DataController, no.
I will unpack the question a little. If you have an existing RESTful CRUD implementation and you want to use Upshot to communicate with it that should be possible with the correct DataProvider. I think the current OData DataProvider is read only at the moment
but I would expect that to change either from the Microsoft side or the community side. If you write the correct DataProvider you can connect upshot to almost anything.
If you are creating a new application with a new service then the DataController with its Submit(Changeset changeset) is probably a better solution if you are planning to use validation, unit of work, or any other core features of SPA.
Mar 15, 2012 02:15 AM|zhangbenrong|LINK
will upshot.js suport WCF RIA Services ?