Yeah if only we could grab that and the origin via the socket constructor… >.>
You could always make your own socket wrapper class, hmm…
Looks awesome overall though!!!
This has nothing to do with Drab and is purely a broken OTP installation, google can assist with that (as I don’t use a mac ^.^;). 
It is not a problem if I want to read the session cookie, I can always clone it in the plug. The issue is I can’t write it anyhow.
Anyway, looks like session will remain read-only in Drab. But it could be good to have some store, session or whatever to exchange informations between controller and commander world.
Elaborate, please!
Well you know the transports used, like on the line:
transport :websocket, Phoenix.Transports.WebSocket
The Phoenix.Transports.WebSocket part is just fulfilling a behaviour, it might be possible to make a module that just delegates back to that one but overrides a few key functions on it to perform the cookie work again (and don’t forget the origin check!), that would be a great standalone library actually…
Ahoy, @OvermindDL1, I’ve just started adding Drab to Unpoly to handle some more interactivity to my search results page that I couldn’t achieve with Unpoly alone.
Things work peachy until Unpoly swaps out my search results page with a different set of search results. Elements that have been decorated with “drab-click” and “drab-change” no longer work! I’ve tried using shared controllers as you suggested, but to no avail…
What code you use to reinitialize Drab onto newly inserted content? Saw that you were the other kid on the block using the Drab + Unpoly combo, hoping you’ve run into this problem before!
You have to actually setup an Unpoly Router to ‘decorate’ the elements with the Drab javascript library again. I’ve been meaning to pull mine out into a Drab addon (DrabUnpoly?) but it’s so tied in with the rest of my stuff and I’ve been so out of time that I’ve not been able to yet. ^.^
@grych Can help with the proper calls to reinitialize elements with Drab, just add those to an Unpoly router on load/unload and so forth.
There is a function Drab.enable_drab_on(element) which reinitializes Drabbed elements. See Drab.Client – drab v0.10.5
up.compiler("#up-results", function() { Drab.enable_drab_on("#up-results") }); does the trick! Thx for the heads up and thx for open-sourcing Drab.
That was it! Thanks much!
There’s actually a compiler/router callback for handling ‘all elements that have been loaded via some kind of ajax call’ that is a convenient place to put such things in.
Hey, I have been trying Drab out.
I have a question about Broadcasting.
I have a genserver doing some stuff, and I would like Drab to update the assigns on a page when an event happens in the GenServer. For instance, when data is added to the genserver I want to push this to the live view using Drab.
I read that it you dont pass the socket to the broadcast function then you need to pass in all assigns and view etc. But I wont really have the data for all assigns, so this doesnt seem like a possibility?
So my question is, what would be the best way to do this?
Can I store the socket in a Drab store and retrive it in the genserver?
Is there some way to get the socket info into other parts of my application without user interaction on the frontend?
Lastly, if I wanted to trigger a drab call from a JS function, like using a timeout to “ping” the Drab event handlers, how would I do that?
Sorry for all the questions, just trying to understand how to use Drab for server side events, not when a users has to interact with the page.
thanks alot
Yes, you can give a topic to any broadcasting function instead of the socket.
And yes, to broadcast poke (update of an assign) you need to give all assigns values. The reason is very simple: every browser may have different state at the same time. Broadcasting poke overwrites all the states to the given one.
This is why I should not do a broadcasting version of poke. I recommend you to use traditional DOM updates (from Drab.Element for example) when broadcasting.
See Allow to broadcast using poke / peek · Issue #60 · grych/drab · GitHub for more.
It is not practical. The socket is just a struct, where the most important information is a PID of the channel process (and in case you are using Drab, the PID of the Drab process).
When browser is disconnected, channel and drab process dies.
There is an idea to replace socket with something more abstract, which identifies a browser. In this case you might send an update to the browser which is disconnected. See 54) ElixirConf US 2018 – Closing Keynote – Chris McCord - #76 by grych
Easy, just use Drab.exec_elixir() method from JS. See docs for Drab.Client.