t.w.c.c.BaseCGIChannelRequest(protocol.Protocol) : class documentation

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

No class docstring
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.
def makeRequest(self, vars): (source)
def writeIntermediateResponse(self, code, headers=None): (source)
Ignore, CGI doesn't support.
def write(self, data): (source)
def finish(self): (source)
def getHostInfo(self): (source)
def getRemoteHost(self): (source)
def abortConnection(self, closeWrite=True): (source)
def registerProducer(self, producer, streaming): (source)
def unregisterProducer(self): (source)
def writeConnectionLost(self): (source)

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.
def readConnectionLost(self): (source)

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.
API Documentation for Twisted, generated by pydoctor at 2011-10-27 16:12:41.