|
|
113.
|
|
|
Upon connection, the server will send the client a list of string elements, signifying the profiles it supports. It is recommended that <code>"none"</code> be included in this list. The client then sends the server a string from this list, telling the server which profile it wants to use. At this point the whole session will use this profile.
|
|
|
type: Content of: <html><body><p>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
specifications/banana.xhtml:177
|
|
|
114.
|
|
|
Once a profile has been established, the two sides may start exchanging elements. There is no limitation on order or dependencies of messages. Any such limitation (e.g. <q>server can only send an element to client in response to a request from client</q>) is application specific.
|
|
|
type: Content of: <html><body><p>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
specifications/banana.xhtml:184
|
|
|
115.
|
|
|
Upon receiving illegal messages, failed handshakes, etc., a Banana client or server should close its connection.
|
|
|
type: Content of: <html><body><p>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
specifications/banana.xhtml:190
|
|
|
118.
|
|
|
The Twisted Zope Interfaces FAQ
|
|
|
type: Content of: <html><body><h1>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
upgrades/2.0/components.xhtml:4 upgrades/2.0/components.xhtml:9
|
|
|
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
|
|
|
124.
|
|
|
The twisted.python.components package is a large amount of on-going maintenance. Using the Zope Interface package also provides a greater level of compatibility between Twisted interfaces and Zope interfaces.
|
|
|
type: Content of: <html><body><p>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
upgrades/2.0/components.xhtml:27
|
|
|
125.
|
|
|
Why did Twisted switch to Zope Interfaces rather than PyProtocols?
|
|
|
type: Content of: <html><body><h3>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
upgrades/2.0/components.xhtml:32
|
|
|
126.
|
|
|
The Zope Interface package was chosen over PyProtocols because of its greater conceptual similarity to twisted.python.components.
|
|
|
type: Content of: <html><body><p>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
upgrades/2.0/components.xhtml:35
|
