Bokeh ceases to stream data after intermittent time interval

[Bryan]

@bel-lau I should first point out this recent reply in another thread:

Problem with streaming of real-time data

Hi @mabo The first thing I will quickly note is that kind of usage, where you call stream from outside the bokeh server, from a separate process, is not really intended usage.[1] In fact, I am somewhat surprised it works in any fashion. In any case, connecting this way has a number of intrinsic disadvantages, including doubling both the storage required for any data (since its now duplicated in the outside process, and the bokeh server), as well as adding an entire additional network leg between…

To reiterate what is said there, this kind of approach (e.g. running a “blank” bokeh server and pushing everything to it from outside processes) is not at all the way the core developers intend for the bokeh server to be used. The bokeh.client has extremely narrow intended applications: 1) testing, and 2) making one time up front tweaks (i.e. per user customizations) to server-generated sessions before embedding them in rendered pages.

Would anyone be willing to share the reasoning behind this change?

The change was made in the server code to simplify it and support better logging. If making a similar change in the client code helps your use case (I doubt it), then we’d be happy to consider a PR. Though again, I cannot stress enough: this kind of usage explicitly dis-encouraged by us (which is why there are no examples of this sort of thing anywhere in the docs or examples) So, I would be much more interested in discussing how to help you restructure your app in a more supported way.