beer
play

BEER Block Extensible Exchange in Rebol What is it? It is a - PowerPoint PPT Presentation

BEER Block Extensible Exchange in Rebol What is it? It is a framework to implement your own Application Protocols It solves the encapsulation, extensibility and flow control problems It was inspired by IETF RFC 3080 and 3081


  1. BEER Block Extensible Exchange in Rebol

  2. What is it? • It is a framework to implement your own “Application Protocols” • It solves the encapsulation, extensibility and flow control problems • It was inspired by IETF RFC 3080 and 3081 • More importantly it allows for non-blocking user-interfaces

  3. What problems does it solve ? • Creation of new application protocols using the same infrastructure, e.g. SMTP , FTP, HTTP solve the same basic problem, but in different ways “The Wheel Reinvented” • BEER brings the best of all under one hood. • Simple Framing • Robust flow control • Asynchrony

  4. Mechanism ESMTP FTP HTTP1.1 BEER Counting Framing Stuffing Blasting Counting with a trailer Binary or Encoding 822-style Binary MIME Dialects Reporting 3-digit 3-digit 3-digit String Pipelining and Asynchrony Pipelining None Channels Chunking Carl Authentication SASL user/pass user/pass challenge TLS Privacy SASL or TLS None Rebol cloak (that’s SSL) Extensibility Some None Some Profiles

  5. What are Profiles ? • They are your “Application Protocol” • You can use blocks or parse to define the syntax and semantics that each channel can use. • Which Profiles are we shipping? • Channel management • FXP - File Transfer Profile • MSP - Message Services Profile (aka LNS)

  6. TCP Session Management on Channel 0 FXP on Channel 1 MSP on Channel 2 Listener Initiator FXP on Channel 3

  7. Channel Exchange Types • 1:1 MSG / RPY • 1:N MSG / ANS + NUL (N can be zero!) • 1:1 MSG / ERR Note: • Channels are processed in parallel = asynchrony • Exchange are processed serially = pipelining

  8. Why do we need it ? • We want to create many types of applications each with different problem domains: • New terms Initiator and Listener • Client-Server (Traditional approach) • P2P (anyone can initiate the requests) • For example: • Network Monitoring Applications • Instant Messaging (think AltMe on Steroids)

  9. What are we doing with it ? (Rasta Controller Demo)

  10. What does it mean for the Rebol community ? • BEER pushes Rebol limits => Rebol is more robust • Uncovered hidden features • Identified issues and requested fixes • Proposed enhancements • Recommending “Idioms” • But more importantly BEER is free as in “free beer” starting today. http://www.whywire.net/share/beer-sdk.tar.gz

  11. Who built it ? Richard Smolak Jaime Vargas Ladislav Mecir

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend