From: Bill Erickson <berick@esilibrary.com>
Date: Tue, 18 Feb 2014 21:29:15 +0000 (-0500)
Subject: eg 2014 browser client
X-Git-Url: https://old-git.evergreen-ils.org/?a=commitdiff_plain;h=cde7b221efe173e6d8404cdc0fa023088814a8d6;p=working%2Frandom.git

eg 2014 browser client

Signed-off-by: Bill Erickson <berick@esilibrary.com>
---

diff --git a/browser_client.txt b/browser_client.txt
index 83ef7b6d2..23543a841 100644
--- a/browser_client.txt
+++ b/browser_client.txt
@@ -7,11 +7,11 @@ Bill Erickson <berick@esilibrary.com>
 
 image:images/jonah-api.jpg[Used The Documented API]
 
-'*' Consarn ye, XULRunner!
-
 Here we see a young Jonah Hill expressing frustration when his 
 decision to choose a seemingly wise course of action backfires.
 
+'*' Consarn ye, XULRunner!
+
 == What's Wrong with XULRunner? ==
 
 [role="incremental"]
@@ -33,12 +33,28 @@ decision to choose a seemingly wise course of action backfires.
 
 == Enter: The Browser ==
 
+  * It will no longer be necessary to install an application to
+    update the client.  It all happens on the server.
+  * Browsers, HTML, and JavaScript are all evolinging and rapidly 
+    improving, with lots of public and corporate momentum.
+  * A wealth of resources
+    ** It's hard to find a software developer that does not have a basic 
+       understanding of HTML and JavaScript.
+    ** Using the same tools lots of others use means any problems we encounter
+    have likely been solved 100 times over by others.  Compared to 
+    XULRunner, the available resources (help, documentation, developers, etc.)
+    is 
+
+Any approach we choose will come with its own set of technical challenges.
+The trick is to find the best feature to technical hurdles ratio.
+
 == How do we avoid the XULRunner pitfalls? ==
 
   * Only use features which are supported by multiple browsers.
 
 == Why Not Another Desktop Client? ==
 
+The tr
 No approach is free of technical hurdles.  As as the browser goes, the 
 benefits to challenges ratio is high.
 
@@ -53,8 +69,34 @@ benefits to challenges ratio is high.
 
 == Staff Client Prototype Project ==
 
+link to report
+http://wiki.evergreen-ils.org/doku.php?id=dev:browser_staff:manifesto
+
 == Future Development ==
 
+  * WebSockets
+  * https://bugs.launchpad.net/evergreen/+bug/1251394
+
+== WebSockets ==
+
+  * Bi-directional, streaming, long-lived connections
+  * multipart/x-mixed-replace on steroids
+
+== WebSockets Streaming Example ==
+
+Comparing Patron Search with traditional XMLHttpRequest and WebSockets.
+
+Skit?
+
+https://docs.google.com/a/esilibrary.com/drawings/d/1U-MaNLBGJJFdfkdEl1zVDFLu8MsZyVq1-ii-7_r8jVM/edit
+
+https://docs.google.com/a/esilibrary.com/drawings/d/1_n1eNuQFUN5rr-21V4jo6rIs-cz9Aj-k75p4yqtcP0Q/edit
+
+== WebSockets Streaming Example ==
+
+  * With 50 results, XMLHttpRequest requires 102 messages, and 
+    WebSockets requires 51 messages.
+
 
 ////
 vim: ft=asciidoc