The Distributed Observer Pattern (Observer Pattern goes PubSub): UDP/Multicast, cache control, etag, 304; Vary/Redirect/303, HTTP tunnelling, Comet, form tunnelling, http header tunnelling in query part, content types, URL forms. JSON header: host UIDs
Entities' public state is conveyed across the network using a pub-sub, peer-to-peer, UDP protocol based on HTTP. Asynchronous, bi-directional, P2P protocol for request/response events, unlike HTTP which relies on order to tie up requests with responses and which doesn't have resources at the client end.
NP talks DOP and tunnelling and is oblivious to its JSON/NN payload
An Entity with UID 123-456 could be found at these URLs:
http://host.foo.com/u/123-456.js http://host.foo.com/path/type/title-for-seo/tag/tag/u/123-456.js http://proxyhost.foo.com//host.foo.com/path/type/title-for-seo/tag/tag/u/123-456.js http://host.foo.com/u/123-456.u http://host.foo.com/#vpsite=123-456
All the text is hints and decorations, not used in dereferencing. You may or may not fetch this from the sourcehost, for example, but from proxyhost - a peer cache. The 'u/xx-yy-zz.js' part always appears at the end. Cacheing is by UID, not by URL. The fourth example is the "content": part only, with "headers": translated into the HTTP headers. The last example isn't a direct link, but a link through a Javascript viewer.
The '.js' Javascript (headers/content) Content-Type is application/javascript. The '.u' pure JSON Content-Type is application/json.
[2278]