WordPress.org

Make WordPress Core

Opened 8 years ago

Closed 6 years ago

Last modified 6 years ago

#23183 closed enhancement (wontfix)

Single Page Application/OData API

Reported by: cportwood Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: General Keywords:
Focuses: Cc:

Description

I am interested in helping out. Are there any plans to move to a Single Page Application model. I know this would take a lot of work as we would have to code a secure Web API into the core (I would go with standard OData service API) but as mobile devices become more critical to web success WordPress needs to find a way to minimize requests and allow for occasionally connected solutions. I know this would be for major release 4 or possibly even 5 depending on the impact to plugin developers but it make a noticeable difference on the scalability of wordpress.

Change History (8)

#1 @cportwood
8 years ago

Base it off the WordPress section offered - https://github.com/MSOpenTech/odataphpprod.

It would allow for plugin developers to be able to choose from a number of existing JavaScript Client Service libraries like Breezejs or UpshotJS. It would also make Microsoft developers more comfortable working on WordPress Plugins and patches.

#2 @cportwood
8 years ago

  • Cc chris_portwood@… added

#3 @nacin
7 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

I think I am going to close this based on a general shift toward Backbone.js and an eventual REST API.

#4 @cportwood
7 years ago

I agree with the move in that direction... Although I find MVVM a better direction I am not seeing UX minded developers embracing it and backbone is by far the most embraced library out there.

#5 @johnimg
6 years ago

  • Resolution wontfix deleted
  • Status changed from closed to reopened

I see OData is still in development but it appears Backbone has not been in the works for a year now.

Note: I am working on integrating Kendo UI with WP and it uses OData. This would make integration much simpler for all users.

Last edited 6 years ago by johnimg (previous) (diff)

#6 @dd32
6 years ago

  • Resolution set to wontfix
  • Status changed from reopened to closed

Backbone is still under active development - https://github.com/jashkenas/backbone
And we're still backing a REST-API at present - https://github.com/wp-api/wp-api

A plugin is welcome to come along and offer an OData API however.

#7 @johnimg
6 years ago

I guess you could call bug fixes active development but better put that would be a support cycle. Windows XP was supported for bug fixes and the like for a long season also but that is not the same thing as active development. I can respect the decision to use Backbone as a supported technology though, even if it is not in active development.

Note: I checked the repository, there are no new branches that I could find. If there are would you please show me the link to the same or a roadmap or evidence of the same?

P.S.
I do see the REST API is in development. While that is nice it is not at all the same thing. Now if we developed a back end RESTful data service that performed the same functionality then the point would be meaningful. The point to oData is not having a restful service. The point is having a CRUD+ interface standard prebuilt. You would not have to wire for read, wire for write, wire for update, wire for delete, wire for (the list goes on) as oData has that all built in standard. Now if WP had RESTdata, a service that had wiring for those purposes then the REST-API would be an actual consideration for replacing oData. At this point it is like trying to replace a hotel foyer with a mud room and coat closet. It's just not the same thing.

#8 @johnimg
6 years ago

P.S.
Look at the docs here so you can get an idea of why people who use oData prefer it and what a great business use case it serves.

http://docs.telerik.com/kendo-ui/using-kendo-with-open-access

Note: See TracTickets for help on using tickets.