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?"
Am I the only one who thinks that acronyms that are normal words just confuse non-technical people?
I mean honestly, I've seen people get over RAM and SDRAM but when I tell them that there's a problem with the BEEP they are going to just flip out.
Is a simple question mark too much to ask for?
It's hard to be religious when certain people are never incinerated by bolts of lightning.
the electricity over IP rfc
why run from Vincenzo?
No.