# \[Screencast\] ActionCable - Part 2 - More Complex Example

**URL:** <https://metaruby.com/t/screencast-actioncable-part-2-more-complex-example/568>\
**Category:** Learning Ruby\
**Created:** [July 18, 2016, 11:28am UTC](https://metaruby.com/t/screencast-actioncable-part-2-more-complex-example/568 "2016-07-18T11:28:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kobaltz](https://metaruby.com/user_avatar/metaruby.com/kobaltz/32/982_2.png) [@kobaltz](https://metaruby.com/u/kobaltz)\
**Post date:** [July 18, 2016, 11:28am UTC](https://metaruby.com/t/screencast-actioncable-part-2-more-complex-example/568/1 "2016-07-18T11:28:24Z")

</div>

Extending the previous episode, we look into making a realtime poll application where users can get live feedback on voting. [https://www.driftingruby.com/episodes/actioncable-part-2-more-complex-example](https://www.driftingruby.com/episodes/actioncable-part-2-more-complex-example)

---

<div class="post-metadata">

**Author:** ![AstonJ](https://metaruby.com/user_avatar/metaruby.com/astonj/32/8_2.png) [@AstonJ](https://metaruby.com/u/AstonJ)\
**Post date:** [July 18, 2016, 1:09pm UTC](https://metaruby.com/t/screencast-actioncable-part-2-more-complex-example/568/2 "2016-07-18T13:09:26Z")

</div>

Nice to see more on this Dave.

Just a quick suggestion, have you thought about doing one on upgrading a Rails 4 app to Rails 5? I think Ryan used to do these 😉

---

<div class="post-metadata">

**Author:** ![kobaltz](https://metaruby.com/user_avatar/metaruby.com/kobaltz/32/982_2.png) [@kobaltz](https://metaruby.com/u/kobaltz)\
**Post date:** [July 18, 2016, 4:56pm UTC](https://metaruby.com/t/screencast-actioncable-part-2-more-complex-example/568/3 "2016-07-18T16:56:47Z")

</div>

I do plan on making an upgrade screencast.

My hesitation has mostly been allowing gems to get updated. I’ve upgraded a lot of my apps to Rails 5 already from the latest Rails 4. It is a task, but much less painless than Rails 2 =\> 3 and Rails 3 =\> 4. I think that the biggest breaking change was Turbolinks Classic to Turbolins 5. However, this can be mitigated with the compatability.js that’s included.

I’ve just been on this huge kick about performance and web sockets lately.