An example of using BEEP is:
Peer1 opens up three channels, using BEEP, such that these same three
channels will accept data coming from the Peer2. Peer 2 in the mean
time opens up another three channels, using BEEP, such that these
different channels will accept data coming from Peer1.So far we have 3
channels each for accepting data (and, it goes without saying 3 channels
each for transmitting data ). And we also need 1 channel that is always
usable for channel control data, between Peer 1 and Peer2.
Now say that Peer2 simply has to much data to send over it's, alotted
three channels, to Peer1. Peer 2, using the control channel, asks Peer
1 if it can borrow two of it's channel for awhile and Peer 1 would
become a receiver of five data channels and a transmitter of only 1
channel. Peer 1 either relinquishes or refuses.
Is this along the lines of what you want to happen?
Thanks
Steven Kurylo wrote:
> On 7/23/06, William Christensen <wchriste@sasktel.net> wrote:
>> Maybe your looking for BEEP (*Blocks Extensible Exchange Protocol) RFC
>> 3080. It's a peer to peer protocol that allows you to create channels
>> over TCP. I believe there are implementations of the BEEP protocol in
>> C and Java. There is also a book called "BEEP: The Definitive Guide" by
>> Marshall T Rose, who is also the author of the BEEP protocol. *
>
> I just read a brief article on BEEP and the start of the rfc; I don't
> even remotely see how it relates to network traffic shaping. It looks
> like a framework for creating p2p application level protocols.
>
> Am I overlooking something? Thanks.
Received on Sun Jul 23 17:16:40 2006
This archive was generated by hypermail 2.1.8 : Fri Sep 08 2006 - 23:26:38 CST