Archived discussions · Captured October 28, 2026

Sharing documents between sessions

joshFeb 27, 2016 #1

Hi,

I’d like to share a document between sessions. I suspect this is easy (based on 0.10.0 docs), but I can’t find an example or the relevant part of the docs in version 0.11.0. A function like “get document by name” or “get data source by name” is the sort of thing I’m looking for.

For example, if I have a sensor producing data, I’d like one process that updates the document and syncs to bokeh server, and then any number of clients can connect and view the updating document. The closest I’ve come to achieving this is having every session has it’s own document and be responsible for updating, so if there are 10 session then there is 10x the data going up to the server.

Regards,

Josh.

⌁ Link to post

Havoc_PenningtonMar 04, 2016 #2

Hi,

This thread may be useful to you:
https://groups.google.com/a/continuum.io/d/msg/bokeh/qVVfCUu_eow/cDZjQcVbBQAJ

Essentially, you can have a server-wide task running that updates all the sessions.

A really great Bokeh feature would be to add an API that does the boilerplate aspects of this for you (as suggested in that thread).

Also more examples/docs of doing this would be helpful to others I believe.

Havoc

···

On Sat, Feb 27, 2016 at 8:52 AM, josh@arbidyne.com wrote:

Hi,

I’d like to share a document between sessions. I suspect this is easy (based on 0.10.0 docs), but I can’t find an example or the relevant part of the docs in version 0.11.0. A function like “get document by name” or “get data source by name” is the sort of thing I’m looking for.

For example, if I have a sensor producing data, I’d like one process that updates the document and syncs to bokeh server, and then any number of clients can connect and view the updating document. The closest I’ve come to achieving this is having every session has it’s own document and be responsible for updating, so if there are 10 session then there is 10x the data going up to the server.

Regards,

Josh.

–

You received this message because you are subscribed to the Google Groups “Bokeh Discussion - Public” group.

To unsubscribe from this group and stop receiving emails from it, send an email to bokeh+unsubscribe@continuum.io.

To post to this group, send email to bokeh@continuum.io.

To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/5a71f19a-78d4-4c2d-a08d-8e69bc095a2c%40continuum.io.

For more options, visit https://groups.google.com/a/continuum.io/d/optout.

–

Havoc Pennington

Senior Software Architect

[External image unavailable in archive]

⌁ Link to post

joshMar 17, 2016 #3

The Happiness demo was exactly what I needed to be looking at: https://github.com/bokeh/bokeh-demos

Now that I know what I’m looking at I see it’s referenced from the Bokeh Server documentation, but for my money the link should be 20 feet high, right att the top

Thanks for your help pointing me in the right direction!

···

On Sunday, February 28, 2016 at 2:25:31 AM UTC+11, jo...@arbidyne.com wrote:

Hi,

I’d like to share a document between sessions. I suspect this is easy (based on 0.10.0 docs), but I can’t find an example or the relevant part of the docs in version 0.11.0. A function like “get document by name” or “get data source by name” is the sort of thing I’m looking for.

For example, if I have a sensor producing data, I’d like one process that updates the document and syncs to bokeh server, and then any number of clients can connect and view the updating document. The closest I’ve come to achieving this is having every session has it’s own document and be responsible for updating, so if there are 10 session then there is 10x the data going up to the server.

Regards,

Josh.

⌁ Link to post

BryanMar 19, 2016 #4

Agreed it could be highlighted better. If you are familiar with ReST/Sphinx and are interested in contributing some docs, the relevant file is:

https://github.com/bokeh/bokeh/blob/master/sphinx/source/docs/user_guide/server.rst

Perhaps a new subsection on "Integrating With Other Web-app Frameworks" ?

Note this example will probably move soon, to main GH repo. We'd like to get rid pf bokeh-demos as a separate thing.

Thanks,

Bryan

···

On Mar 17, 2016, at 5:59 PM, josh@arbidyne.com wrote:

The Happiness demo was exactly what I needed to be looking at: https://github.com/bokeh/bokeh-demos

Now that I know what I'm looking at I see it's referenced from the Bokeh Server documentation, but for my money the link should be 20 feet high, right att the top

Thanks for your help pointing me in the right direction!

On Sunday, February 28, 2016 at 2:25:31 AM UTC+11, jo...@arbidyne.com wrote:
Hi,

I'd like to share a document between sessions. I suspect this is easy (based on 0.10.0 docs), but I can't find an example or the relevant part of the docs in version 0.11.0. A function like "get document by name" or "get data source by name" is the sort of thing I'm looking for.

For example, if I have a sensor producing data, I'd like one process that updates the document and syncs to bokeh server, and then any number of clients can connect and view the updating document. The closest I've come to achieving this is having every session has it's own document and be responsible for updating, so if there are 10 session then there is 10x the data going up to the server.

Regards,

Josh.

--
You received this message because you are subscribed to the Google Groups "Bokeh Discussion - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bokeh+unsubscribe@continuum.io.
To post to this group, send email to bokeh@continuum.io.
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/be9bc68d-f0cb-45d8-a616-3f66fc85bae8%40continuum.io\.
For more options, visit https://groups.google.com/a/continuum.io/d/optout\.

⌁ Link to post

systemJul 21, 2021 #5

⌁ Link to post

End of archived discussion · Replies are disabled