Age | Commit message (Collapse) | Author |
|
getsockopt(..., SO_ERROR) on the second spin of connect(). That'd get better results out of it.
|
|
|
|
|
|
|
|
|
|
actually intend to implement them anyway...
|
|
|
|
|
|
|
|
|
|
|
|
handle, and some small helpers; more helpers to come.
|
|
|
|
|
|
|
|
step in the proper direction.)
|
|
up, wouldn't it ?
|
|
BStream using it, in case one never wants to use the readString() or peekByte() methods.
|
|
debugging purposes.
|
|
|
|
|
|
|
|
|
|
method to String.
|
|
|
|
and a potential client makes sense. Also packing requests and responses into structures / classes is probably a good idea.
|
|
something to do.
|
|
|
|
|
|
Connection header
(I hate RFCs, they never mentionned keep-alive in the list of potential headers)
|
|
|
|
I'm not really sure I fully like the way I'm designing this, but I guess it could be solved with an HTTP/HTML helper class around the Action class.
However, the HTTP server awfully need reference counting, so it doesn't go away before all of the workers disappear, which means a bit of a redesign of the Listener template.
|
|
anymore: the task manager takes care of this now.
|
|
unit test for this...
|
|
task manager, and actually implementing it properly.
|
|
to be performed from the task manager.
|
|
differently.
|
|
|
|
|
|
|
|
class, but, meh.
|
|
stick on another one's thread, if needed. (and it is)
|
|
TaskScheduler.
The idea is that we need to support multiple task managers from multiple threads.
So that revamp means we now should be able to support that, except the TaskScheduler needs to implement a round robin system, to distribute tasks across multiple task managers. But at least, the fundamental redesign to permit this is here.
|
|
|
|
escaped characters.
|
|
|
|
being read, as it needs to go thru the BStream.
|
|
from Handle...
|
|
|
|
|