PyBEEP Project

[phil hunt]

On 10 Mar 2002 09:58:22 -0800, Gabriel Wachob <gwachob at wachob.com> wrote:
>It was pointed out to me that not everyone may know what BEEP is. BEEP
>is an IETF spec (RFC 3080/3081):
>
>"
>BEEP, the Application Protocol Framework, ... offers advanced features
>such as:
>
>* a standard application layer that supports dynamic, pluggable
>application "profiles" (protocols)
>* peer-to-peer, client-server, or server-to-server capabilities 
>* multiple channels over a single authenticated session 
>* support for arbitrary MIME payloads, including XML 
>"
>
>and from RFC 3080:
>
>a generic application protocol kernel for
>connection-oriented, asynchronous interactions called the BEEP
>(Blocks Extensible Exchange Protocol) core.  BEEP permits
>simultaneous and independent exchanges within the context of a single
>application user-identity, supporting both textual and binary
>messages.

Does this mean it is some sort of RPC framework?

-- 
<"><"><"> Philip Hunt <philh at comuno.freeserve.co.uk> <"><"><">
"I would guess that he really believes whatever is politically 
advantageous for him to believe." 
                        -- Alison Brooks, referring to Michael
                              Portillo, on soc.history.what-if