| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Goals:
Understand the load we are able to handle with the discussion API for when the mobile app is released.
- What can the server handle?
- What kind of usage patterns will be introduced with the mobile app?
- Understand the the overhead between the discussion API and the ruby forums code.
- Does the Discussion API perform better, worse, or on par with the browser's forums?
...
- Default page size for the browser is 25 while the mobile device will be using 10. It is possible that more requests could be sent for the same amount of information.
- Push notifications
- There is a possibility for a different usage pattern to look out for. If there is a popular thread, bursts of requests can be expected.
- Increased forum usage as there is currently no notifications for the browser.
- The browser can display the Threads, Response, and Comments all at once. The mobile app treats all three of these as separate views. It is possible that more requests could be sent for the same amount of information.
- General Usage. Discussions on mobile could naturally increase discussion forums usage.
...
Things that were left out:
Moderator actions
- Pin Thread - Not implemented
- Open/Close Thread -Not implemented
- Endorsed - Not Implemented
Course topics - This will be addressed at another time.
...
/threads/
GET: Anchor /threads/get /threads/get
| /threads/get | |
| /threads/get |
...