Differences

This shows you the differences between two versions of the page.

--- dev:meetings:future_of_staff_client [2013/01/30 16:28] – [Agenda] dbs
+++ dev:meetings:future_of_staff_client [2022/02/10 13:34] (current) – external edit 127.0.0.1
@@ Line 7: / Line 7: @@
   * 18:00:00 Wednesday, February 6, 2013 in UTC
+  * [[http://evergreen-ils.org/meetings/evergreen/2013/evergreen.2013-02-06-13.00.html|Minutes]]
+  * [[http://evergreen-ils.org/meetings/evergreen/2013/evergreen.2013-02-06-13.00.txt|Minutes (text)]]
+  * [[http://evergreen-ils.org/meetings/evergreen/2013/evergreen.2013-02-06-13.00.log.html|Raw meeting log]]
 ===== Agenda =====
   * Do we still need a staff client?
       * Go entirely web-based?
+          * local sqlite db for client
+              * scheduled uploads to main db at intervals
+              * client-side data checking
+              * no direct manipulation or update of data by staff-client user.
       * Have a minimal staff client for things like label printing?
   * Move as much as possible to chrome (client-side XUL)
@@ Line 21: / Line 29: @@
       * [[http://blog.esilibrary.com/2013/01/14/exploring-websockets-and-evergreen/|Exploring WebSockets and Evergreen]]
       * [[http://blog.esilibrary.com/2013/01/21/exploring-websockets-and-evergreen-ii-long-lived-connections/|Exploring WebSockets and Evergreen II: Long-lived Connections]]
+      * [[http://blog.esilibrary.com/2013/02/06/exploring-websockets-and-evergreen-iii-proof-of-concept/|Exploring WebSockets and Evergreen III: Proof of Concept]]
+  * Objective third-party performance analysis to identify bottlenecks in the system. Future decisions on changes to staff client or other pieces of the Evergreen architecture could be based on evidence from this analysis. (proposal by Kathy Lussier)