summaryrefslogtreecommitdiff
path: root/includes
AgeCommit message (Collapse)Author
2011-11-25Adding a 'HandlePrinter' Handle type, to easily print out the results of a ↵Pixel
handle, and some small helpers; more helpers to come.
2011-11-25We need the buffered streams to be detacheablePixel
2011-11-25Consts are good.Pixel
2011-11-24Making strings being able to read from their end.Pixel
2011-11-23That would make way more sense to the fromConst Buffer to have its size set ↵Pixel
up, wouldn't it ?
2011-11-23Adding the isA<>() template / method to the IO proxy, and optimizing the ↵Pixel
BStream using it, in case one never wants to use the readString() or peekByte() methods.
2011-11-21GeneralException() will now trace the callstack and store this, for ↵Pixel
debugging purposes.
2011-11-19Having the ability to create buffers from const memory.Pixel
2011-11-19Having String.set returning this.Pixel
2011-11-19Handling more Connection tags, separated with commas; and adding the 'split' ↵Pixel
method to String.
2011-11-19Fixing a few very stupid bugs.Pixel
2011-11-18Starting to re-organize the HTTP code a bit. Sharing code between the server ↵Pixel
and a potential client makes sense. Also packing requests and responses into structures / classes is probably a good idea.
2011-11-18Got this one wrong; one need to get the refcount to 0 to delete itself.Pixel
2011-11-17HTTP server's first real test, alongside multiple taskmanager threads.Pixel
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.
2011-11-17Cleaning some code, redesigning a bit the stack allocation problem from the ↵Pixel
task manager, and actually implementing it properly.
2011-11-17Introducing the fact we need a more efficient stack allocator, and that it's ↵Pixel
to be performed from the task manager.
2011-11-17Since tasks can be on different task managers, one has to signal them a bit ↵Pixel
differently.
2011-11-16Adding the Regex class.Pixel
2011-11-16Seems clang is picky. I don't know if I like or hate this compiler yet.Pixel
2011-11-16I hate doing this, but, well. Maybe I should design a memory allocator ↵Pixel
class, but, meh.
2011-11-16And with the new TaskScheduler system, let's add a way for a new task to ↵Pixel
stick on another one's thread, if needed. (and it is)
2011-11-16Kind of a big revamp of the TaskMan / Task model, in order to introduce a ↵Pixel
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.
2011-11-16This function doesn't exist.Pixel
2011-11-16Of course, to be viable, the ReadOnly and WriteOnly classes need to derive ↵Pixel
from Handle...
2011-11-15Adding two Handle restricters: ReadOnly and WriteOnly.Pixel
2011-11-15Making the String class a bit more tolerent of NULL strings.Pixel
2011-11-15Adding a potential event to cancel a forced read/write, such as a timeout.Pixel
2011-11-15Moving code around for the Listener, in order to avoid too much template code.Pixel
2011-11-15Adding the forceRead/Write methods, to circumvent the potential problem that ↵Pixel
a file descriptor can do less than being asked.
2011-11-15Moving the static yield from Task.h to Task.cc. You don't want to throw an ↵Pixel
exception from a .h file...
2011-11-15Fixing the Socket code a bit, effectively making the listener system working.Pixel
2011-11-14Some more basic work on the HTTP server. Some of the main ideas are not ↵Pixel
fleshed up, and writing the actual server should now be sort of straightforward.
2011-11-14Making sure the typecasting on Handles worked properly.Pixel
2011-11-14As always, doing stuff during a constructor is a bad idea, especially if it ↵Pixel
contains a potential task switch.
2011-11-14If I'm having a wrapper class around Handles, it's for a reason...Pixel
2011-11-14Adding 'isEmpty' helper. We probably want a 'put' method also. That could ↵Pixel
come in handy.
2011-11-13Adding the skeleton of an HTTP server; still work in progress though: it ↵Pixel
still needs coding, and won't work as it. And it needs a unit test.
2011-11-13Adding an opaque pointer to the generic Socket listener.Pixel
2011-11-13Adding buffered streams; mainly for string parsing.Pixel
2011-11-13Adding isEOF() to Buffers (and cleaning code a tiny bit)Pixel
2011-11-13Adding seek and tell aliases to rseek and rtell.Pixel
2011-11-12Adding seekable buffers. Probably would need a few more tests in the Handles ↵Pixel
unit test.
2011-11-09Adding 'Output' objectPixel
2011-10-27Fixing a few oddities, and having the 'clean' target cleaning LuaJIT as well.Pixel
2011-10-26Adding Lua.Pixel
2011-10-26Protecting the IO class a bit more, and adding the raw filename paradigm for ↵Pixel
at least the Input class.
2011-10-25Adding the FileSystem global class with mkdir, and adding the writeString ↵Pixel
method to Handles. Also preparing the inclusion of Lua by adding LuaJIT.
2011-10-18Stopping the Task Manager when the Main Task exits, and having a switch to ↵Pixel
turn that off.
2011-10-18libcoro seems to be doing really spurious things when not using the standard ↵Pixel
functions. Switching out libcoro for the native Fibers interface for Win32. Switching out the asm version for the ucontext version for Linux.
2011-10-18Adding a few more asserts, and using the proper function calls (ntohs ↵Pixel
instead of htons - which should be fundamentally the same, but, *shrug*)