Permalink
Browse files

re-including demo

  • Loading branch information...
1 parent 0aafcfd commit 15908d1d5c0c3193061badd84c30cee45f1efce7 @michielbdejong committed Jul 27, 2012
Showing with 2 additions and 2 deletions.
  1. +2 −2 index.html
View
@@ -142,9 +142,9 @@
<h2>Project status</h2>
<p>The current implementation of UserAddress is at <a href="https://github.com/unhosted/useraddress">gh:unhosted/useradddress</a>. <strong>This is only a proof-of-concept, not production-ready.</strong> We will discuss on in the fedsocweb CG what should be done with it. If we decide we want to run this as a production service, then we need to find someone who can do that (probably one person full-time), and get funding for it.</p>
<h2>Cross-origin services</h2>
- <p>Since we are in the business of breaking down domain barriers, this service works over a WebSocket (sockjs-compatible) that has not same-origin policy. That means you can create a widget on any web app, no matter whether it's hosted (server-side) and unhosted (client-side), and query the central index server from there. You may of course also run a local instance, but if we set up one central service, then we have the benefit of scaling the index nicely, and have better heuristic results on free-text name searches. The Websocket responds incrementally on anything you send it, so it's easy to use it for as-you-type search. You may also combine it with a local (logged-in) search on the app, so that public results get mixed with private logged-in search results.</p>
+ <p>Since we are in the business of breaking down domain barriers, this service works over a WebSocket (sockjs-compatible) that has no same-origin policy. That means you can create a widget on any web app, no matter whether it's hosted (server-side) or unhosted (client-side), and query the central index server from there. You may of course also run a local instance, but if we set up one central service, then we have the benefit of scaling the index nicely, and have better heuristic results on free-text name searches. The Websocket responds incrementally on anything you send it, so it's easy to use it for as-you-type search. You may also combine it with a local (logged-in) search on the app, so that public results get mixed with private logged-in search results.</p>
<h2>Demo</h2>
- <p>A little demo is below. It has no error reporting yet, but at least the examples should work.</p>
+ <p>A little demo is below. It has no error reporting yet, and may fail without warning. Remember, this is only a proof-of-concept, not even an alpha service. But at least the examples should work.</p>
<div id="searchWidget" style="display:block">
<h3>To prime, search something like::</h3>
<ul>

0 comments on commit 15908d1

Please sign in to comment.