metadata

Check-in [6fca4f6c93]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Minor typo
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256:6fca4f6c93fb68b6b0d33eb5e8e42a8521b22ef16b0d632e6868810cd9e46b93
User & Date: vandys 2018-06-24 13:19:51
Context
2018-06-24
18:07
Bringup; CORS and comment updates check-in: a43eaed8f7 user: vandys tags: trunk
13:19
Minor typo check-in: 6fca4f6c93 user: vandys tags: trunk
2018-06-19
23:57
fs extras cleanup check-in: 09f1914815 user: vashon tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to README.md.

9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
about metadata, you have to do it off-browser.

Doing this in the browser would be much, much better.

Anyway.

This server accepts requests on /metadata/<who>.json[?gen=<int>]
and send back JSON of "key: value" of all the values received
from <who>'s metadata.  It fires up a stream to <who> and pulls
metadata from it, when possible sharing its information across
multiple clients.

If your "gen" is less than the current generation of information, your
request is completed immediately with the current values.  Otherwise
your request is held (i.e., long polling) until the stream changes.
Typically your web app is XHR'ing these, and updating the UI with the
current information as it changes.







|









9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
about metadata, you have to do it off-browser.

Doing this in the browser would be much, much better.

Anyway.

This server accepts requests on /metadata/<who>.json[?gen=<int>]
and sends back JSON of "key: value" of all the values received
from <who>'s metadata.  It fires up a stream to <who> and pulls
metadata from it, when possible sharing its information across
multiple clients.

If your "gen" is less than the current generation of information, your
request is completed immediately with the current values.  Otherwise
your request is held (i.e., long polling) until the stream changes.
Typically your web app is XHR'ing these, and updating the UI with the
current information as it changes.