| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
response if a request handler fails to make a response to the client
|
| |
|
| |
|
| |
|
|
|
|
| |
for wantread and wantwrite
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
success
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
to listener.onconnect.
|
| |
|
|
|
|
| |
can now be tostring()'d
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
s/xml-not-well-formed/not-well-formed/ as per latest bis drafts.
|
|
|
|
| |
main componentmanager file.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
handler, in case onconnect sends data and the socket is still writeable (causing stack overflow into sendbuffer()/onconnect())
|
| |
|
| |
|
|
|
|
| |
even if it doesn't match an outstanding request
|
|
|
|
| |
disconnect handling.
|
| |
|
|
|
|
| |
option 'component_address'.
|
| |
|
|
|
|
| |
the event loop
|
|
|
|
| |
darkhippo)
|
|
|
|
| |
fields (thanks dersd)
|