# ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ # ┃ ██████ ██████ ██████ █ █ █ █ █ █▄ ▀███ █ ┃ # ┃ ▄▄▄▄▄█ █▄▄▄▄▄ ▄▄▄▄▄█ ▀▀▀▀▀█▀▀▀▀▀ █ ▀▀▀▀▀█ ████████▌▐███ ███▄ ▀█ █ ▀▀▀▀▀ ┃ # ┃ █▀▀▀▀▀ █▀▀▀▀▀ █▀██▀▀ ▄▄▄▄▄ █ ▄▄▄▄▄█ ▄▄▄▄▄█ ████████▌▐███ █████▄ █ ▄▄▄▄▄ ┃ # ┃ █ ██████ █ ▀█▄ █ ██████ █ ███▌▐███ ███████▄ █ ┃ # ┣━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫ # ┃ Copyright (c) 2017, the Perspective Authors. ┃ # ┃ ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌ ┃ # ┃ This file is part of the Perspective library, distributed under the terms ┃ # ┃ of the [Apache License 2.0](https://www.apache.org/licenses/LICENSE-2.0). ┃ # ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛ from tornado.websocket import WebSocketHandler, WebSocketClosedError from tornado.ioloop import IOLoop import perspective __doc__ = """ Perspective ships with a pre-built Tornado handler that makes integration with `tornado.websockets` extremely easy. This allows you to run an instance of `Perspective` on a server using Python, open a websocket to a `Table`, and access the `Table` in JavaScript and through ``. All instructions sent to the `Table` are processed in Python, which executes the commands, and returns its output through the websocket back to Javascript. ### Python setup To use the handler, we need to first have a `Server`, a `Client` and an instance of a `Table`: ```python SERVER = Server() CLIENT = SERVER.new_local_client() ``` Once the server has been created, create a `Table` instance with a name. The name that you host the table under is important — it acts as a unique accessor on the JavaScript side, which will look for a Table hosted at the websocket with the name you specify. ```python TABLE = client.table(data, name="data_source_one") ``` After the server and table setup is complete, create a websocket endpoint and provide it a reference to `PerspectiveTornadoHandler`. You must provide the configuration object in the route tuple, and it must contain `"perspective_server"`, which is a reference to the `Server` you just created. ```python from perspective.handlers.tornado import PerspectiveTornadoHandler app = tornado.web.Application([ # ... other handlers ... # Create a websocket endpoint that the client JavaScript can access (r"/websocket", PerspectiveTornadoHandler, {"perspective_server": SERVER, "check_origin": True}) ]) ``` Optionally, the configuration object can also include `check_origin`, a boolean that determines whether the websocket accepts requests from origins other than where the server is hosted. See [Tornado docs](https://www.tornadoweb.org/en/stable/websocket.html#tornado.websocket.WebSocketHandler.check_origin) for more details. ### JavaScript setup Once the server is up and running, you can access the Table you just hosted using `perspective.websocket` and `open_table()`. First, create a client that expects a Perspective server to accept connections at the specified URL: ```javascript const websocket = await perspective.websocket("ws://localhost:8888/websocket"); ``` Next open the `Table` we created on the server by name: ```javascript const table = await websocket.open_table("data_source_one"); ``` `table` is a proxy for the `Table` we created on the server. All operations that are possible through the JavaScript API are possible on the Python API as well, thus calling `view()`, `schema()`, `update()` etc. on `const table` will pass those operations to the Python `Table`, execute the commands, and return the result back to JavaScript. Similarly, providing this `table` to a `` instance will allow virtual rendering: ```javascript await viewer.load(table); ``` `perspective.websocket` expects a Websocket URL where it will send instructions. When `open_table` is called, the name to a hosted Table is passed through, and a request is sent through the socket to fetch the Table. No actual `Table` instance is passed inbetween the runtimes; all instructions are proxied through websockets. This provides for great flexibility — while `Perspective.js` is full of features, browser WebAssembly runtimes currently have some performance restrictions on memory and CPU feature utilization, and the architecture in general suffers when the dataset itself is too large to download to the client in full. The Python runtime does not suffer from memory limitations, utilizes Apache Arrow internal threadpools for threading and parallel processing, and generates architecture optimized code, which currently makes it more suitable as a server-side runtime than `node.js`. """ class PerspectiveTornadoHandler(WebSocketHandler): """`PerspectiveTornadoHandler` is a `perspective.Server` API as a `tornado` websocket handler. Use it inside `tornado` routing to create a `perspective.Server` that can connect to a JavaScript (Wasm) `Client`, providing a virtual interface to the `Server`'s resources for e.g. ``. You may need to increase the `websocket_max_message_size` kwarg to the `tornado.web.Application` constructor, as well as provide the `max_buffer_size` optional arg, for large datasets. # Security `PerspectiveTornadoHandler` is a reference integration with no authentication, authorization, origin enforcement, or rate limiting, and is not safe to expose to untrusted networks — see [`SECURITY.md`](https://github.com/perspective-dev/perspective/blob/master/SECURITY.md) for the full threat model. # Arguments - `loop`: An optional `IOLoop` instance to use for scheduling IO calls, defaults to `IOLoop.current()`. - `executor`: An optional executor for scheduling `perspective.Server` message processing calls from websocket `Client`s. # Examples >>> server = psp.Server() >>> client = server.new_local_client() >>> client.table(pd.read_csv("superstore.csv"), name="data_source_one") >>> app = tornado.web.Application([ ... (r"/", MainHandler), ... (r"/websocket", PerspectiveTornadoHandler, { ... "perspective_server": server, ... }) ... ]) """ def check_origin(self, origin): return True def initialize( self, perspective_server=perspective.GLOBAL_SERVER, loop=None, executor=None, max_buffer_size=None, ): self.server = perspective_server self.loop = loop or IOLoop.current() self.executor = executor if max_buffer_size is not None: self.request.connection.stream.max_buffer_size = max_buffer_size def open(self): def write(msg): try: self.write_message(msg, binary=True) except WebSocketClosedError: self.close() def send_response(msg): self.loop.add_callback(write, msg) self.session = self.server.new_session(send_response) def on_close(self) -> None: self.session.close() del self.session def on_message(self, msg: bytes): if not isinstance(msg, bytes): return if self.executor is None: self.session.handle_request(msg) else: self.executor.submit(self.session.handle_request, msg)