From 22342392e21065d21a390cc041990fe75219010c Mon Sep 17 00:00:00 2001 From: Peter Parente Date: Thu, 25 Feb 2016 12:30:47 -0500 Subject: [PATCH] Clarify statement about use of notebook server Address comment https://github.com/jupyter/enhancement-proposals/pull/12#discussion_r52857796 (c) Copyright IBM Corp. 2016 --- .../jupyter-kernel-gateway-incorporation.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/jupyter-kernel-gateway-incorporation/jupyter-kernel-gateway-incorporation.md b/jupyter-kernel-gateway-incorporation/jupyter-kernel-gateway-incorporation.md index 8660fe45..b649dea1 100644 --- a/jupyter-kernel-gateway-incorporation/jupyter-kernel-gateway-incorporation.md +++ b/jupyter-kernel-gateway-incorporation/jupyter-kernel-gateway-incorporation.md @@ -13,12 +13,12 @@ People are creating novel applications and libraries that use Jupyter kernels as These applications have two important properties in common: -1. They spawn kernels using provisioning APIs that run separate, and often remote, from the user-facing web applications themselves. +1. They spawn kernels using provisioning APIs that run separate, and often remote, from the user-facing applications themselves. 2. They communicate with kernels using Websockets rather than directly with ZeroMQ. -Originally, these applications spawned entire Jupyter Notebook servers in order to request kernels using notebook HTTP API and communicate with them over Websockets. This approach is less than ideal, however, for various reasons: +Some of these application have spawned (or still do spawn) entire Jupyter Notebook servers on the backend in order to request kernels using notebook HTTP API and communicate with them over Websockets. This approach is less than ideal, however, for various reasons: -1. The notebook UI is exposed but only the programmatic UI is used +1. The notebook UI is exposed, but only the programmatic UI is used 2. The notebook authentication mechanism is form- and cookie-based and meant for humans, not programmatic clients 3. The notebook transport mechanisms and APIs serve the notebook user experience, and are not meant to be replaced or extended to support other clients