Kinda related to all the issues posted about changing a Notebook with 2
different users to some degree.
It could be possible to block Iframe from sending websocket events. And
eventually from receiving any.
However this would make impossible some features that always persist the
result: Filters a
"Can this behavior be customized? Does some of you have found a
workaround?"
--> Work around is to create 2 distinct paragraphs with the same content
and export them as Iframe separately
On Wed, Jul 27, 2016 at 9:53 AM, Patrick Duflot <
patrick.duf...@iba-group.com> wrote:
> Hello Zeppelin,
>
Hello Zeppelin,
We were trying out Zeppelin. We created notebooks and then we share them as
iframe to embed as dashboards in our app.
We have JavaScript widgets that are bound to the Spark context to automatically
refresh the data on input changes. Everything was fine until we noticed that
when
