There is no security concern that I can see, since the script will be created and maintained only by the KA developers, and the only communication to and from the worker exists through a "postMessage" system.Ĭreate a simple (or not :P) API script on the kasandbox domain that programmers can import into their webpage and use. By 'making it a change in x' instead, we show it as y (x + 3) + 0. If we keep it as a change in y, we have y x + 3, so it is easy to see the y intercept. the y intercept is 3 (set x0) and the x intercept is -3 (set y 0). This means that a "POST" fetch to the new API could successfully be made from a Worker script sourced on the domain. This is going to be true for all functions, so lets start with a linear equation y x + 3. The upside is that Web Workers do not inherit the same-origin rules as the document that makes them. Modern Browsers now support "Web Workers," which work as isolated scripts that can be imported from any valid domain (like that complies with the document's same-origin rules. A script tag simply will not suffice for this.
With the new API, however, a "POST" request is needed to send a Go query to the backend. This was so because the domain " is blocked by the live editor.
Now, thanks to the new Go-powered API, fetching a program's discussion posts or a user's scratchpads is simply not possible.īefore, fetches could only be made using "JSONP" request, where the user would create a "script" tag with a special addition to the URL that would pass the API data to a JavaScript function. Over the past few years, many in the programming community have expressed remorse over the departure of the old API, which could be accessed legally from Khan Academy's HTML editor.
0 kommentar(er)
