You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current behaviour: Access to cell results occurs through the API at a common URL for all results (based on cell ID). This means that cell results can be embedded via a URL of the form:
which returns a JSON description of the cell and its results. However, this approach suffers from two limitations:
It requires interpretation of the JSON results to get a specific output form (e.g., the HTML console output), and thus can not be embedded in an IFRAME.
It is not compatible with API instances protected by http-authentication
Proposed behavior: Thorough some mechanism to be discussed, users flag a cell result as publishable. They are provided with a URL that can be viewed by anyone, embedded in an external html page, etc... Critically, the set of published cells would be collected under a specific path (e.g., /api/v1/published/...) making it possible to expose them to the public or at least a different set of users with the right proxy configuration.
Some ideas on how this could be implemented:
Attach a toggle to Python, SQL, Plot, and Scala cells that publishes the cell result.
Provide a button on console output that publishes the cell result and displays the URL.
Add an explicit "Publish" cell or incorporate into the UNLOAD cell a feature for publishing the results of an earlier cell.
The text was updated successfully, but these errors were encountered:
Starting a thread to discuss how to implement this properly (Tagging @mrb24 @lordpretzel @julianafreire @heikomuller @soniacq @CarlosaBauti for discussion).
Current behaviour: Access to cell results occurs through the API at a common URL for all results (based on cell ID). This means that cell results can be embedded via a URL of the form:
which returns a JSON description of the cell and its results. However, this approach suffers from two limitations:
Proposed behavior: Thorough some mechanism to be discussed, users flag a cell result as publishable. They are provided with a URL that can be viewed by anyone, embedded in an external html page, etc... Critically, the set of published cells would be collected under a specific path (e.g.,
/api/v1/published/...
) making it possible to expose them to the public or at least a different set of users with the right proxy configuration.Some ideas on how this could be implemented:
The text was updated successfully, but these errors were encountered: