Balau - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2011-11-25	We need the buffered streams to be detacheable	Pixel

2011-11-25	Consts are good.	Pixel

2011-11-24	Making strings being able to read from their end.	Pixel

2011-11-23	That would make way more sense to the fromConst Buffer to have its size set ↵	Pixel
	up, wouldn't it ?
2011-11-23	Adding 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-21	GeneralException() will now trace the callstack and store this, for ↵	Pixel
	debugging purposes.
2011-11-19	Having the ability to create buffers from const memory.	Pixel

2011-11-19	Having String.set returning this.	Pixel

2011-11-19	Handling more Connection tags, separated with commas; and adding the 'split' ↵	Pixel
	method to String.
2011-11-19	Fixing a few very stupid bugs.	Pixel

2011-11-18	Starting 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-18	Got this one wrong; one need to get the refcount to 0 to delete itself.	Pixel

2011-11-17	HTTP 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-17	Cleaning some code, redesigning a bit the stack allocation problem from the ↵	Pixel
	task manager, and actually implementing it properly.
2011-11-17	Introducing the fact we need a more efficient stack allocator, and that it's ↵	Pixel
	to be performed from the task manager.
2011-11-17	Since tasks can be on different task managers, one has to signal them a bit ↵	Pixel
	differently.
2011-11-16	Adding the Regex class.	Pixel

2011-11-16	Seems clang is picky. I don't know if I like or hate this compiler yet.	Pixel

2011-11-16	I hate doing this, but, well. Maybe I should design a memory allocator ↵	Pixel
	class, but, meh.
2011-11-16	And 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-16	Kind 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-16	This function doesn't exist.	Pixel

2011-11-16	Of course, to be viable, the ReadOnly and WriteOnly classes need to derive ↵	Pixel
	from Handle...
2011-11-15	Adding two Handle restricters: ReadOnly and WriteOnly.	Pixel

2011-11-15	Making the String class a bit more tolerent of NULL strings.	Pixel

2011-11-15	Adding a potential event to cancel a forced read/write, such as a timeout.	Pixel

2011-11-15	Moving code around for the Listener, in order to avoid too much template code.	Pixel

2011-11-15	Adding the forceRead/Write methods, to circumvent the potential problem that ↵	Pixel
	a file descriptor can do less than being asked.
2011-11-15	Moving the static yield from Task.h to Task.cc. You don't want to throw an ↵	Pixel
	exception from a .h file...
2011-11-15	Fixing the Socket code a bit, effectively making the listener system working.	Pixel

2011-11-14	Some 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-14	Making sure the typecasting on Handles worked properly.	Pixel

2011-11-14	As always, doing stuff during a constructor is a bad idea, especially if it ↵	Pixel
	contains a potential task switch.
2011-11-14	If I'm having a wrapper class around Handles, it's for a reason...	Pixel

2011-11-14	Adding 'isEmpty' helper. We probably want a 'put' method also. That could ↵	Pixel
	come in handy.
2011-11-13	Adding 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-13	Adding an opaque pointer to the generic Socket listener.	Pixel

2011-11-13	Adding buffered streams; mainly for string parsing.	Pixel

2011-11-13	Adding isEOF() to Buffers (and cleaning code a tiny bit)	Pixel

2011-11-13	Adding seek and tell aliases to rseek and rtell.	Pixel

2011-11-12	Adding seekable buffers. Probably would need a few more tests in the Handles ↵	Pixel
	unit test.
2011-11-09	Adding 'Output' object	Pixel

2011-10-27	Fixing a few oddities, and having the 'clean' target cleaning LuaJIT as well.	Pixel

2011-10-26	Adding Lua.	Pixel

2011-10-26	Protecting the IO class a bit more, and adding the raw filename paradigm for ↵	Pixel
	at least the Input class.
2011-10-25	Adding 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-18	Stopping the Task Manager when the Main Task exits, and having a switch to ↵	Pixel
	turn that off.
2011-10-18	libcoro 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-18	Adding a few more asserts, and using the proper function calls (ntohs ↵	Pixel
	instead of htons - which should be fundamentally the same, but, shrug)
2011-10-18	Fixing Darwin compilation:	Pixel
	-) Using clang instead of gcc for the native target (sigh) -) Fixing libeio (sigh) -) "Fixing" the connect() call in Sockets because Darwin is stupid (SIIIIIIIGH) Although the Threads unit test isn't working properly.