2011-09-03, 18:22
Since the HTTP API is deprecated will this eventually be removed from XBMC builds or will it always be available but simply won't be improved upon or changed?
2011-09-04, 08:29
As far as I know there aren't any concrete plans to remove the HTTP API, so I suspect it will be around for a while yet. However I wouldn't develop any new software that uses it.
JR
JR
2011-11-29, 02:46
So why did you remove the docs then. If the API exists it needs to be documented.
Until the JSONRPC fully duplicates the functionality of the HTTP API you need to keep the HTTP API and DOCUMENT IT! Some people are still using it.
There are forks of XBMC like BOXEE that still haven't caught up with JSONRPC, and the XBMC docs are the only docs. You NEED to keep this info around for reference. EDEN isn't even officially out yet and not everyone is going to upgrade right away.
Until the JSONRPC fully duplicates the functionality of the HTTP API you need to keep the HTTP API and DOCUMENT IT! Some people are still using it.
There are forks of XBMC like BOXEE that still haven't caught up with JSONRPC, and the XBMC docs are the only docs. You NEED to keep this info around for reference. EDEN isn't even officially out yet and not everyone is going to upgrade right away.
2011-11-29, 03:31
I agree I use the http api for my complete builds till its replaced entirely why act like it isnt there....
My guess is for less confusion of where XBMC is going but the http api is still integrated into the builds from what I can see.
My guess is for less confusion of where XBMC is going but the http api is still integrated into the builds from what I can see.
2011-11-29, 10:40
wuench Wrote:So why did you remove the docs then.
http://wiki.xbmc.org/index.php?title=Web...r_HTTP_API
JR
2011-11-29, 12:22
That would be me who changed stuff on the wiki. We have a lot of outdated information, even stuff that still mentions the original xbox, and I've been tasked with cleaning this stuff up. When I do so I don't delete anything, but rather use redirects. When you are taken to a new page after being redirected you can click on the link under the title to go back to that original page and then hit the history tab.
http://wiki.xbmc.org/index.php?title=Web...ldid=27300
So everything is still there and accessible.
Since it's such a big task updating the wiki, so anything out of date as of pre-Eden (and anything not recommended for use going-forward) is a target for being redirected or removed from the main pages/listings/etc. The HTTP API is now unsupported, so.. yeah.. the normal pages for it are redirected and it's no longer listed on the main navigation template. BUT none of it is deleted. Same with the old xBox pages.
I'm even thinking of making an "Archive" namespace in the wiki for when whole pages get outdated, so they can be out of the way but more accessible, but right now there's a lot of other stuff to do on the wiki.
EDIT: I've restored the page for now. Thinking about it, there shouldn't be any harm in having the page itself still working like normal. Maybe I'll make that "Archive" namespace after all.
http://wiki.xbmc.org/index.php?title=Web...ldid=27300
So everything is still there and accessible.
Since it's such a big task updating the wiki, so anything out of date as of pre-Eden (and anything not recommended for use going-forward) is a target for being redirected or removed from the main pages/listings/etc. The HTTP API is now unsupported, so.. yeah.. the normal pages for it are redirected and it's no longer listed on the main navigation template. BUT none of it is deleted. Same with the old xBox pages.
I'm even thinking of making an "Archive" namespace in the wiki for when whole pages get outdated, so they can be out of the way but more accessible, but right now there's a lot of other stuff to do on the wiki.
EDIT: I've restored the page for now. Thinking about it, there shouldn't be any harm in having the page itself still working like normal. Maybe I'll make that "Archive" namespace after all.
