Will BEEP Simplify Network Programming?

hensley writes "There is a (not quite) new effort by the IETF to standardize a framework for network applications, called BEEP, the Blocks Extensible Exchange Protocol. Standardized in RFC3080, it takes care of all lower level tasks an application level protocol has to like framing, authentication and capabilities negotiation in a modular and lightweight way. In the current issue of Internet Packet Journal (a quite nice and free-as-in-beer technical publication by Cisco) is a well written Introduction to this framework. Why isn't anyone adopting this protocol besides some Java libraries like beep4j and PermaBEEP and a C library called RoadRunner. I couldn't find any applications based on this protocol, regardless of it's promised capabilities. Is everybody still inventing his own application layer protocol?"

Comments

I used it once...

[Anonvmous Coward]

I used beep in a programming course in High School. Unfortunately, every time I used it people shouted "nosound!".

That C Library doesn't actually use BEEP

[Kaz Riprock]

The guys who designed the RoadRunner C Library modified the protocol. They called it Minimal Extensible Exchange Protocol. They then implemented the protocol twice to speed up the system calls.

This way RoadRunner goes really fast with
MEEPMEEP!(thp-thp-thp-thpppp) this was all just a funny lie

Re:That C Library doesn't actually use BEEP

[red_dragon]

Given that we're discussing this within Slashdot and its context, I suggest that we rename it to Minimal Extensible Exchange Protocol Toolkit. Additionally, this protocol should perform every action within a single, long transaction encapsulating multiple exchanges, e.g.:

MEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEPT!

Re:stateful connection

[mindstrm]

No state is maintained from one ftp connection to the next.
No state is maintained from one telephone call to the next.
No state is maintained from one quake session to the next.

By that definition, all protocols are stateless.