> > One major one is that BXXP doesn't say anything about what it transports > or what its interaction model is (other than session oriented). One of > BXXP's goals was to allow for a protocol where the actual elements > were unlimited. The outcome is that BXXP can frame and multiplex > anything that can be encoded in a MIME body. The channel maintenance > stuff is in XML but that doesn't mean the actual protocol elements > have to be... Neither does Webmux, it multiplexes any arbitrary bi-directional byte streams and includes a credit scheme to maximize throughput while minimizing deadlock conditions. Playing devil's advocate, -- Justin Chapweske - Noodler, Cyrus Intersoft http://www.cyrusintersoft.com/Received on Wednesday, 5 April 2000 11:54:24 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:41:39 GMT