# Experience from slow hotel connection

**URL:** <https://meta.discourse.org/t/experience-from-slow-hotel-connection/44421>\
**Category:** Feature\
**Created:** [2016年五月18日 03:41 UTC](https://meta.discourse.org/t/experience-from-slow-hotel-connection/44421 "2016-05-18T03:41:04Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [2016年五月19日 10:27 UTC](https://meta.discourse.org/t/experience-from-slow-hotel-connection/44421/2 "2016-05-19T10:27:00Z")

</div>

This is all a bit peculiar since discourse, as a JavaScript app, **_excels_ at exactly this kind of spotty connection scenario.** It is not sending whole web pages and assets over the wire, it is only requesting the minimal set of JSON data necessary to redraw the screen with JavaScript.

To be honest, we haven’t focused on it particularly because we are naturally very good at it by dint of our original design choices; it would be like asking a cheetah if it could please just run a tiny bit faster.

Anyway, we are mixing two requests here:

1. Displaying “loading…” indicators for **read-only display actions** that could take a little while

2. Confirming that saves happen for **save write actions**.

I’ve used Discourse a fair bit on smartphone with connections going in and out and I’ve never lost a reply. So that’s concerning, but we’d need a repro. With a bad enough connection _anything_ is possible, so who knows.

Probably the best thing to do is focus on case #1, and identify places where we should show a loading spinner if the network is _so_ slow and _so_ unreliable that even getting a bit of JSON over the wire will take a while. These are surely much more common overall.

---

_[View the full topic](https://meta.discourse.org/t/experience-from-slow-hotel-connection/44421)._