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

Age	Commit message (Collapse)	Author
2011-11-25	Consts are good.	Pixel

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

2011-11-23	Making sure that the mingw32 target isn't too broken (it is, but that's a ↵	Pixel
	step in the proper direction.)
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	Adding error 500s support.	Pixel

2011-11-19	Of course, spaces are optionnal...	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	Updating libev's timestamp after we (potentially) wait a long time for ↵	Pixel
	something to do.
2011-11-18	Making the debug build to increase libev's debugness too.	Pixel

2011-11-18	Got this one wrong; one need to get the refcount to 0 to delete itself.	Pixel

2011-11-17	Adding a few reasons why we'd get an HTTP 400 error, and fixing the ↵	Pixel
	Connection header (I hate RFCs, they never mentionned keep-alive in the list of potential headers)
2011-11-17	Look at that. It seems that, indeed, IPv6 CAN get very retarded.	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	Forgot to remove this; we shouldn't free the stack from the Task itself ↵	Pixel
	anymore: the task manager takes care of this now.
2011-11-17	And adding the round robin system to the task scheduler. Now to write some ↵	Pixel
	unit test for this...
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	clang actually managed to pick up a bug...	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	Even if an URI doesn't have variables embedded, it still may contained ↵	Pixel
	escaped characters.
2011-11-16	Adding a simple 'daemon name' for our output.	Pixel

2011-11-16	Using the new WriteOnly class in the HttpServer, to protect the socket from ↵	Pixel
	being read, as it needs to go thru the BStream.
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	Basic POST support done; multipart/form-data is yet to be finalized.	Pixel

2011-11-15	A bit more work on the HTTP server. Only the parsing of the POST method is ↵	Pixel
	remaining. Multipart is going to be cumbersome.
2011-11-15	Making the String class a bit more tolerent of NULL strings.	Pixel

2011-11-15	The HTTP server now takes advantage of that new parameter of forceRead/Write.	Pixel

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

2011-11-15	Balancing code a bit out of the constructor.	Pixel

2011-11-15	Actually, that's the proper fix for the Listener system, otherwise accept() ↵	Pixel
	will never stop, rendering the stop method of the Listener inneffective.
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-15	Fixing a few parsing mistakes.	Pixel

2011-11-15	Initial parsing of the Http request should now be there.	Pixel

2011-11-14	Typo.	Pixel