Friday, May 21st, 2010

TeleHash: Real-time wire protocol for JSON

Category: JSON

<p>TeleHash is a brand new “wire protocol for exchanging JSON in a real-time and fully decentralized manner.”

If you are into switches and Erlang, it will look maybe a bit familiar, with entries such as:

javascript
< view plain text >
  1. // basic Telex with example command
  2. {
  3.     "_ring": 43723,
  4.     ".see": ["5.6.7.8:23456", "11.22.33.44:11223"],
  5. }
  6.  
  7. // Telex with example signals
  8. {
  9.     "+end": "a9993e364706816aba3e25717850c26c9cd0d89d",
  10.     "+foo": "0beec7b5ea3f0fdbc95d0dd47f3c5bc275da8a33"
  11. }
  12.  
  13. // Telex of a normal JSON object sent between to Switches
  14. {
  15.     "_to": "1.2.3.4:5678",
  16.     "_line": 63546230,
  17.     "profile_image_url": "http://a3.twimg.com/profile_images/852841481/Untitled_3_normal.jpg",
  18.     "created_at": "Sat, 08 May 2010 21:46:23 +0000",
  19.     "from_user": "pelchiie",
  20.     "metadata": {
  21.         "result_type": "recent"
  22.     },
  23.     "to_user_id": null,
  24.     "text": "twitter is dead today.",
  25.     "id": 13630378882,
  26.     "from_user_id": 12621761,
  27.     "geo": null,
  28.     "iso_language_code": "en",
  29.     "source": "<a href="http://twitter.com/">web</a>"
  30. }

More details:

TeleHash enables applications to connect directly and participate as servers on the edge of the network. It is designed to efficiently route and distribute small bits of data in order for applications to discover each other directly or in relation to events around piece of shared content. The core benefits of TeleHash over other similar platforms and protocols is that it is both generic (not tied to any specific application or content structures) and is radically decentralized with no servers or points of central control.

It works by sending and receiving very simple small bits of JSON via UDP using an easy routing system based on Kademlia, a proven and popular Distributed Hash Table. Everything within TeleHash is routed based on a generic SHA hash, usually of something specific to an application or something common like a URL.

Wow :)

Related Content:

Posted by Dion Almaer at 9:35 am
3 Comments

++++-
4 rating from 2 votes

3 Comments »

Comments feed TrackBack URI

Looks interesting, although I am not sure if telecom influenced terminology is a good idea.

Comment by ragjunk — May 21, 2010

Wow, json bittorrent is only a matter of time. Maybe CDNs will be a thing of the past…

Comment by rdza — May 21, 2010

Yes, this is very exiting. Good time to be in the cutting edge of technology. JSON, AJAX, and Bittorrent sound delicious together.

Comment by LeetRage — May 23, 2010

Leave a comment

You must be logged in to post a comment.