|
|
3.
|
|
|
Banana is an efficient, extendable protocol for sending and receiving s-expressions. A s-expression in this context is a list composed of byte strings, integers, large integers, floats and/or s-expressions.
|
|
|
type: Content of: <html><body><p>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
specifications/banana.xhtml:16
|
|
|
5.
|
|
|
The banana protocol is a stream of data composed of elements. Each element has the following general structure - first, the length of element encoded in base-128, least signficant bit first. For example length 4674 will be sent as <code>0x42 0x24</code>. For certain element types the length will be omitted (e.g. float) or have a different meaning (it is the actual value of integer elements).
|
|
|
type: Content of: <html><body><p>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
specifications/banana.xhtml:24
|
|
|
6.
|
|
|
Following the length is a delimiter byte, which tells us what kind of element this is. Depending on the element type, there will then follow the number of bytes specified in the length. The byte's high-bit will always be set, so that we can differentiate between it and the length (since the length bytes use 128-base, their high bit will never be set).
|
|
|
type: Content of: <html><body><p>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
specifications/banana.xhtml:32
|
|
|
8.
|
|
|
Given a series of bytes that gave us length N, these are the different delimiter bytes:
|
|
|
type: Content of: <html><body><p>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
specifications/banana.xhtml:42
|
|
|
18.
|
|
|
The next 8 bytes are the float encoded in IEEE 754 floating-point <q>double format</q> bit layout. No length bytes should have been defined.
|
|
|
type: Content of: <html><body><dl><dd>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
specifications/banana.xhtml:62
|
|
|
48.
|
|
|
The <code>"pb"</code> profile is intended for use with the Perspective Broker protocol, that runs on top of Banana. Basically, it converts commonly used PB strings into shorter versions, thus minimizing bandwidth usage. It starts with a single byte, which tells us to which string element to convert it, and ends with the delimiter byte, <code>0x87</code>, which should not be prefixed by a length.
|
|
|
type: Content of: <html><body><p>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
specifications/banana.xhtml:128
|
|
|
119.
|
|
|
Twisted components system in 2.0
|
|
|
type: Content of: <html><body><h2>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
upgrades/2.0/components.xhtml:11
|
|
|
120.
|
|
|
Twisted code's own use of the <code class="API">twisted.python.components</code> package has been updated to use <a href="http://www.zope.org/Wikis/Interfaces/FrontPage">Zope Interfaces</a> in the 2.0 release.
|
|
|
type: Content of: <html><body><p>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
upgrades/2.0/components.xhtml:13
|
|
|
121.
|
|
|
New code developed starting with the 2.0 release of Twisted Core should use Zope Interfaces directly rather than using the twisted.python.components package.
|
|
|
type: Content of: <html><body><p>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
upgrades/2.0/components.xhtml:18
|
|
|
123.
|
|
|
Why did Twisted switch to Zope Interfaces?
|
|
|
type: Content of: <html><body><h3>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
upgrades/2.0/components.xhtml:24
|
