Protocol /
Channel
Protocol.Channel History
Hide minor edits - Show changes to output
Changed line 3 from:
For an explanation of this subprotocol, see [[Main/Advertisements]].
to:
For an explanation of this subprotocol, see [[Protocol/Advertisements]].
Changed lines 1-2 from:
to:
Subprotocol name: @@ripple-channel@@.
For an explanation of this subprotocol, see [[Main/Advertisements]].
For an explanation of this subprotocol, see [[Main/Advertisements]].
Changed lines 3-11 from:
Channel Query
[
"channel-query"
]
Channel List
[
"channel-query"
]
Channel List
to:
Channel List Request
Changed lines 6-8 from:
"channel-list": [
(channel data structures)
]
(
to:
"type": "channel-list-request",
"request-id": (integer)
"request-id": (integer)
Changed lines 11-17 from:
Channel Data Structure
(string)
Channel Subscribe
(string)
Channel Subscribe
to:
Channel List
Changed lines 14-16 from:
"channel-subscribe": [
(channel data structures)
]
to:
"type": "channel-list",
"request-id": (integer)
"body": [
(channel data structures)
]
"request-id": (integer)
"body": [
(channel data structures)
]
Changed lines 22-23 from:
Channel Unsubscribe
to:
Channel Data Structure
(string)
Channel Subscribe
(string)
Channel Subscribe
Changed lines 30-32 from:
"channel-unsubscribe": [
(channel data structures)
]
to:
"type": "channel-subscribe",
"body": [
(channel data structures)
]
"body": [
(channel data structures)
]
Changed lines 37-38 from:
Channel Ad
to:
Channel Unsubscribe
Changed lines 40-44 from:
"channel-ad": {
"content": (URI),
"source": (Ripple ID),
"channels": [
(channel data structures)
"channels": [
(channel data structures)
to:
"type": "channel-unsubscribe",
"body": [
(channel data structures)
"body": [
(channel data structures)
Deleted lines 43-46:
("units": (URI),)
("onion": (routing onion data structure),)
}
Added lines 46-66:
Channel Ad
{
"type": "channel-ad",
"from": [
(list of nodes on the sending host that are potential intermediaries
to the ad's source for interested nodes on the receiving host)
]
"body": {
"content": (URI),
"source": (Ripple ID),
"channels": [
(channel data structures)
]
("min-amount": (decimal),
"units": (URI),)
("onion": (routing onion data structure),)
}
}
Changed line 72 from:
* Perhaps there needs to be a way to send address @@channel-ad@@ to multiple nodes on the same host simultaneously in a single message...?
to:
* Perhaps there needs to be a way to address @@channel-ad@@ to multiple nodes on the same host simultaneously in a single message...?
Added lines 1-62:
Extension name: @@ripple-channel@@.
Channel Query
[
"channel-query"
]
Channel List
{
"channel-list": [
(channel data structures)
]
}
Channel Data Structure
(string)
Channel Subscribe
{
"channel-subscribe": [
(channel data structures)
]
}
Channel Unsubscribe
{
"channel-unsubscribe": [
(channel data structures)
]
}
Channel Ad
{
"channel-ad": {
"content": (URI),
"source": (Ripple ID),
"channels": [
(channel data structures)
]
("max-amount": (decimal),)
("units": (URI),)
("onion": (routing onion data structure),)
}
}
Notes:
* content URI should be HTTP-accessible and contain the content of the ad, so hosts don't have to transfer the same ad content over and over
* URI also acts as ID for the ad
* To save bandwidth, a host is not required to send the same @@channel-ad@@ to a node (on another host) more than once. (Same means same URI.)
* Perhaps there needs to be a way to send address @@channel-ad@@ to multiple nodes on the same host simultaneously in a single message...?
Channel Query
[
"channel-query"
]
Channel List
{
"channel-list": [
(channel data structures)
]
}
Channel Data Structure
(string)
Channel Subscribe
{
"channel-subscribe": [
(channel data structures)
]
}
Channel Unsubscribe
{
"channel-unsubscribe": [
(channel data structures)
]
}
Channel Ad
{
"channel-ad": {
"content": (URI),
"source": (Ripple ID),
"channels": [
(channel data structures)
]
("max-amount": (decimal),)
("units": (URI),)
("onion": (routing onion data structure),)
}
}
Notes:
* content URI should be HTTP-accessible and contain the content of the ad, so hosts don't have to transfer the same ad content over and over
* URI also acts as ID for the ad
* To save bandwidth, a host is not required to send the same @@channel-ad@@ to a node (on another host) more than once. (Same means same URI.)
* Perhaps there needs to be a way to send address @@channel-ad@@ to multiple nodes on the same host simultaneously in a single message...?