For one thing, the machine is a server, just dial in the ip to your mobile phone and pull out your bookmarks, or any other named Json bundle. Secondly, get some free table space on the web and keep your bookmarks on the web table space, perfectly secure, then just dial in the server and grab your stuff to the phone. Or like tweets, you can access public table space from your phone, in each cse you get a Json stream, and your phone browsers gets what to do.
But with everything organized as web wide named graphs, down to the null single element graph, the client jumps into any namespace of the moment. So his service provider, having one of these open source engines, keeps the table updated with the latest news, science, politics, entertainment, music, etc. The key values move slowly, the various indexes to them are arbitrarily nested or partitioned. We get huge warehouses of data,video,audio; more or less stuck in one spot, but a variety of nested indexing graphs, mobile users can dial in the name space they want; bots maintain maximum distribution of indices.
No comments:
Post a Comment