Boost logo

Boost :

From: shelarcy (shelarcy_at_[hidden])
Date: 2003-03-03 20:56:48

On Mon, 3 Mar 2003 18:17:45 +0100, Wesley W. Terpstra <terpstra_at_ito.tu-> wrote:

How about BEEP ?

It's not only P2P protocol, but also refactoring of some protocols.

#XML Watch: Bird's-eye BEEP

Part 1 of an introduction to the Blocks Extensible Exchange Protocol
standard of the IETF

Part 2 of an introduction to the Blocks Extensible Exchange Protocol

#Beep BEEP!

> On Wed, Feb 12, 2003 at 06:11:59PM -0500, Jason House wrote:
>> Once I heard there was a generic socket library in development, I
>> thought I'd add
>> a quick feature request. I would like to see the ability to have
>> multiple
>> streams through the same socket.
>> This boils down to providing two distinct benefits.
>> 1: Programs can easily perform complex communications over a single
>> port.
>> 2: Without multiple streams, problems can occur when there are multiple
>> clients
>> behind a proxy connecting to a host outside of the proxy. If the client
>> only
>> forms a single connection to the host, there won't be a problem because
>> the random
>> source port will differentiate each stream. So, when multiple clients
>> connect to
>> a host from behind a proxy, the host can only differentiate each stream
>> by the
>> random source port. So, when the clients form a second connection to
>> the host,
>> each stream gets differentiated from each other, but there is no mapping
>> of random
>> source port ot the distinct client.
> What you are asking for here is:
> ... in my slightly biased opinion. ;-)
> This gives you a stackable transport framework which includes (among
> other
> things) a multiplexed channel.
> This project is still really new, but is shaping up nicely.
> However, it has no relation to boost and is primarily targetted at
> building
> distributed hash tables (p2p apps) that can go through any data channel.

shelarcy <shelarcy_at_[hidden]> 

Boost list run by bdawes at, gregod at, cpdaniel at, john at