[HN Gopher] Beep Core protocol central, RFC 3080/3081, BEEP prof...
       ___________________________________________________________________
        
       Beep Core protocol central, RFC 3080/3081, BEEP profiles, BEEP
       implementation
        
       Author : mindcrime
       Score  : 17 points
       Date   : 2024-01-17 17:56 UTC (5 hours ago)
        
 (HTM) web link (www.beepcore.org)
 (TXT) w3m dump (www.beepcore.org)
        
       | kstrauser wrote:
       | What is this, why would I want to use it, and why aren't other
       | people using it?
        
         | urbandw311er wrote:
         | Very good question. I hope somebody more knowledgeable than me
         | can step in and answer.
        
         | wmf wrote:
         | BEEP provides authentication and mulitplexes streams over a
         | single TCP connection. It's like a version of HTTP/2 that never
         | took off.
        
           | jauntywundrkind wrote:
           | It was discussed on the hybrid-bidirectional (HyBi) mailing
           | list, as a candidate for where after http to go.
           | 
           | HTTP2 is a fine example. The HyBi mailing list seems to have
           | culminated most noticeably in the creation of websockets.
           | https://datatracker.ietf.org/wg/hybi/about/
           | 
           | With webtransport over quic, I feel like we might finally be
           | able to go where BEEP was leading us.
        
         | yau8edq12i wrote:
         | As far as I can tell, the linked webpage explains at least the
         | first two points clearly. Could you elaborate on what you think
         | is missing?
        
         | mindcrime wrote:
         | I was fascinated with BEEP for a few days in like 2005 or so.
         | Never found anything particular to use it for though. But I was
         | reminded of it by the discussion of the Willow Protocol that's
         | also ongoing. Not because the two protocols have much in common
         | per-se, but just the "meta" aspect where BEEP is less a
         | protocol you use "out of the box" but a protocol for building
         | application level protocols.
         | 
         | The Wikipedia summary may explain the general gist of it better
         | than the beepcore page itself:
         | 
         |  _Profiles, channels and a framing mechanism are used in BEEP
         | to exchange different kinds of messages. Only content type and
         | encoding are defaulted by the specification leaving the full
         | flexibility of using a binary or textual format open to the
         | protocol designer. Profiles define the functionality of the
         | protocol and the message syntax and semantics. Channels are
         | full-duplex pipes connected to a particular profile. Messages
         | sent through different channels are independent from each other
         | (asynchronous). Multiple channels can use the same profile
         | through one connection._
        
       | ipython wrote:
       | Total blast from the past. Xgrid[0] used BEEP for its inter-node
       | communication protocol. I haven't thought about any of this for
       | almost 20 years now...
       | 
       | [0] https://en.wikipedia.org/wiki/Xgrid
        
       | gbraad wrote:
       | This page still exists? That had been more than 10 years... me
       | remembers a time jabber was regarded as an alternative to xmlrpc
        
       | meepmorp wrote:
       | I remember being interested in this for a couple days back when
       | it was BXXP.
        
       ___________________________________________________________________
       (page generated 2024-01-17 23:00 UTC)