Part of twisted.web2.channel.cgi View Source View In Hierarchy
Known subclasses: twisted.web2.channel.cgi.CGIChannelRequest, twisted.web2.channel.fastcgi.FastCGIChannelRequest, twisted.web2.channel.scgi.SCGIChannelRequest
Implements interfaces: twisted.internet.interfaces.IHalfCloseableProtocol
| Method | makeRequest | Undocumented |
| Method | writeIntermediateResponse | Ignore, CGI doesn't support. |
| Method | write | Undocumented |
| Method | finish | Undocumented |
| Method | getHostInfo | Undocumented |
| Method | getRemoteHost | Undocumented |
| Method | abortConnection | Undocumented |
| Method | registerProducer | Undocumented |
| Method | unregisterProducer | Undocumented |
| Method | writeConnectionLost | Notification of the write connection being closed. |
| Method | readConnectionLost | Notification of the read connection being closed. |
Inherited from Protocol:
| Method | dataReceived | Called whenever data is received. |
| Method | connectionLost | Called when the connection is shut down. |
Inherited from BaseProtocol (via Protocol):
| Method | makeConnection | Make a connection to a transport and a server. |
| Method | connectionMade | Called when a connection is made. |
Notification of the write connection being closed.
This will never be called for TCP connections as TCP does not support notification of this type of half-close.Notification of the read connection being closed.
This indicates peer did half-close of write side. It is now the responsiblity of the this protocol to call loseConnection(). In addition, the protocol MUST make sure a reference to it still exists (i.e. by doing a callLater with one of its methods, etc.) as the reactor will only have a reference to it if it is writing.
If the protocol does not do so, it might get garbage collected without the connectionLost method ever being called.