# How discourse stays online (Message Bus, Faye, Long Polling)

**URL:** https://meta.discourse.org/t/how-discourse-stays-online-message-bus-faye-long-polling/3238
**Category:** Development
**Created:** [February 16, 2013, 8:20pm UTC](https://meta.discourse.org/t/how-discourse-stays-online-message-bus-faye-long-polling/3238 "2013-02-16T20:20:50Z")
**Posts on this page:** 1
**Showing post:** 22

<div class="post-metadata">

### Author: ![eggie5](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eggie5/32/115481_2.png) [@eggie5](https://meta.discourse.org/u/eggie5)
#### Post date: [January 27, 2015, 2:04am UTC](https://meta.discourse.org/t/how-discourse-stays-online-message-bus-faye-long-polling/3238/22 "2015-01-27T02:04:08Z")

</div>

Yeah, the whole backend is powered by message\_bus. The android/ios client long-polls. Not sure if this is the best use of message\_bus, but It works w/o the added complexity of web sockets. The major win is that it fits in our existing rails stack. The only disadvantage i’ve come across so far is that I can’t find an elegant way to support the typing indicator.

[http://www.eggie5.com/58-real-time-messenging-w-ruby-ios-android](http://www.eggie5.com/58-real-time-messenging-w-ruby-ios-android)

---

_[View the full topic](https://meta.discourse.org/t/how-discourse-stays-online-message-bus-faye-long-polling/3238)._