Age | Commit message (Collapse) | Author |
|
threads that are created on startup.
|
|
|
|
-) Removed Assert()
-) Added AAssert(), IAssert(), RAssert(), TAssert() and Failure()
-) Reworked all asserts in the code, and added meaningful messages to them.
-) Changed the way the startup code is generated; BALAU_STARTUP is no longer necessary.
|
|
|
|
|
|
=(String) operator.
|
|
anything as a variable; also adding a checkTemplate() method to assert a few things onto a template after loading it.
|
|
loop; also the Queue<> template changed for a naive but std-less implementation.
|
|
|
|
|
|
|
|
|
|
actually intend to implement them anyway...
|
|
|
|
|
|
handle, and some small helpers; more helpers to come.
|
|
|
|
|
|
|
|
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.
|
|
|
|
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.
|
|
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.
|
|
|
|
from Handle...
|
|
|
|
|
|
|
|
|
|
a file descriptor can do less than being asked.
|
|
exception from a .h file...
|
|
|
|
fleshed up, and writing the actual server should now be sort of straightforward.
|
|
|
|
contains a potential task switch.
|
|
|