|
def | __init__ |
|
def | connect |
|
def | getfile |
|
def | putheader |
|
def | getreply |
|
def | close |
|
def | __init__ |
|
def | connect |
|
def | getfile |
|
def | getreply |
|
def | close |
|
|
| send |
|
| putrequest |
|
| endheaders |
|
| set_debuglevel |
|
| file |
| hmm. More...
|
|
| headers |
|
| putheader |
|
def httplib.HTTP.getreply |
( |
|
self, |
|
|
|
buffering = False |
|
) |
| |
Compat definition since superclass does not define it.
Returns a tuple consisting of:
- server status code (e.g. '200' if all goes well)
- server "reason" corresponding to status code
- any RFC822 headers in the response from the server
def httplib.HTTP.getreply |
( |
|
self, |
|
|
|
buffering = False |
|
) |
| |
Compat definition since superclass does not define it.
Returns a tuple consisting of:
- server status code (e.g. '200' if all goes well)
- server "reason" corresponding to status code
- any RFC822 headers in the response from the server
hmm.
messy. if status==-1, then self.file is owned by us. well... we aren't explicitly closing, but losing this ref will do it
if getresponse() ever closes the socket on a bad request, then we are going to have problems with self.sock should we keep this behavior? do people use it? keep the socket open (as a file), and return it
The documentation for this class was generated from the following file:
- code/googleappengine-read-only/python/google/appengine/dist27/gae_override/httplib.py