in reply to BLOGGING and/or WIKI modules for Dancer2

FWIW, websockets are The Best® way to do live updates and such in a web GUI. Ajax can only pull (client initiated request) but websockets can pull and push (server sends data without being asked and they have *much* smaller overhead for long running connections). With Ajax, you'll always have to be asking the server, should I update, should I update? Works fine of course and I do it all the time. I'd love to switch to websockets in many places but I'm not a websocket dev yet (only toyed with it to date) so I can't give more advice or caveats.

Update: Corion mentioned something below that I’m also going to try and sounds easier. I’ve been playing with Mojo and this kind of stuff – Writing websocket chat using Mojolicious Lite. I was going to write a log file tailer with it as my first production project but R&D is verrrrrryyyyy far down on my work list for awhile now (and I have no free time at home either).

  • Comment on Re: BLOGGING and/or WIKI modules for Dancer2

Replies are listed 'Best First'.
Re^2: BLOGGING and/or WIKI modules for Dancer2
by Corion (Patriarch) on Dec 13, 2016 at 15:15 UTC

    Personally, I found Server-sent Events / EventSource much easier as it is unidirectional and has less features/security issues like scanning your internal network.

    With both, the server can notify the client of changes and send the changed data.

[reply]

      Looks wonderful. I am out of the loop. Thanks for mentioning it.

[reply]
[reply]

      has less features/security issues like scanning your internal network.

      Hi, whats this now?

[reply]

        Using WebRTC WebSockets, you can instruct the browser to connect to arbitrary IP addresses within your local network to arbitrary ports and speak arbitrary TCP protocols to it. So you don't even need DNS rebinding but can write and deliver a port scanner in HTML+Javascript.

[reply]

In Section Seekers of Perl Wisdom