No that would not be workable. A Bokeh application (associated with an endpoint) is really a factory for creating new Documents and sessions for those Documents. When the endpoint is hit, the app code is run and a new Document and session are created, and the browser is then connected to the session.
You can certainly push a new document and session to a running Bokeh server with the
bokeh.client API, but:
- they are not associated with any app endpoint, they just add a “free floating” session that someone could embed or connect to using the long, explicit session URL
- any callbacks would not run on the Bokeh server! Tthe process that created and pushed the session could start its own blocking event loop so that it could service any callbacks. But this is very unwieldy, and is why the client API was never meant to be used this way