XBlock and RESTful architecture

[chemseddine zaafrane]

I 'm preparing a documentation for my project and i want to know if there is a RESTful architecture with XBlock or not, i've been looking so long and i couldn't find a proper answer

[Ned Batchelder]

Currently, XBlock is only an in-process Python API.  We've long wanted to make them remotable, so that an XBlock could execute on another machine, or in another language, or in another security context.  But that hasn't been built yet.

--Ned.

On Mon, Feb 27, 2017 at 2:53 PM, chemseddine zaafrane <chemseddin...@gmail.com> wrote:

I 'm preparing a documentation for my project and i want to know if there is a RESTful architecture with XBlock or not, i've been looking so long and i couldn't find a proper answer

--
You received this message because you are subscribed to the Google Groups "General Open edX discussion" group.
To view this discussion on the web visit https://groups.google.com/d/msgid/edx-code/d0b79706-3aee-429e-8491-973ea6eb612c%40googlegroups.com.

[chemseddine zaafrane]

thanks for your quick reply Ned, however i found this wiki that seems to talk about a RESTful XBlocks but i couldn't get a proper idea about it

[Ned Batchelder]

I see! That page was last edited 3.5 years ago (David Baumgold edited this page on Oct 28, 2013).  It's not useful.  I will remove it.

Sorry for the confusion.

--Ned.

--
You received this message because you are subscribed to the Google Groups "General Open edX discussion" group.

To view this discussion on the web visit https://groups.google.com/d/msgid/edx-code/fc1268ed-c836-43de-a159-b89b87829e6f%40googlegroups.com.

[Armando Fox]

At one point, wasn't there an XBlock that implemented the client side of an LTI connection, so that the server side of the XBlock could be written as an LTI Service endpoint? If the endpoint is secured, the LTI call could embed whatever arbitrary information the client-side code can extract from the Python runtime. (Here "client" actually means the server-side piece running on edx.org, which would essentially become a proxy/shim that forwards calls to the "real" server implemented as an LTI Service endpoint, if that makes sense.)