libbu++.git - System level, general purpose C++ library.

Age	Commit message (Collapse)	Author
2009-02-24	Woot, the cache system now supports intellegent sync'ing. It will ask the cache	Mike Buland
	about each object that it has and weather or not to sync it. This will probably be made optional in the future.
2009-02-24	Whoa, lots of updates. Md5 is more general, nids, cache, cachestore, and	Mike Buland
	cachestorenids all support synchronizing now. Url is pretty much done.
2009-01-27	Hey, I think that'll fix some things valgrind was bitching about. Apparently	Mike Buland
	BitString is...not so good...I may have to rewrite big chunks.
2009-01-16	They keys can be accessed now for all stores that support it, they pretty much	Mike Buland
	all should, but they don't really haaave to.
2009-01-16	Ok...we'll try this change up of the cache system. It now takes two pointers,	Mike Buland
	one to a Calc and one to a Store. It takes ownership of the two objects, and deletes them when it gets cleaned up.
2009-01-05	I mergered Bu::CPtr into Bu::Cache as Bu::Cache::Ptr. This makes more sense to	Mike Buland
	me, is much less messy, and makes the syntax work a little better for me as well. What the hell was a CPtr? Who knows, but a Cache::Ptr, that makes sense. Also, fewer includes to deal with now, just need Cache and you're set. Oh, also, made Cache::Ptr behave much more like a regular pointer, they can be assigned now, as well as created empty (NULL).
2008-12-20	All of the basic, core workings of the Cache are complete, and tested. Even	Mike Buland
	added some more tests and whatnot. A lot happened, but I can't remember everything. Also, Bu::File reports errors in more error cases.
2008-12-13	The Calc should be functional, and is being called by the Cache itself. The	Mike Buland
	Bu::CacheCalc still needs to reference the Bu::Cache so that it can make the changes it needs to.
2008-12-03	Alright, the caching system now passes the basic CRUD tests with arbitrary	Mike Buland
	keytypes. It doesn't yet use the stackable CacheStore concept, but the code is all in place to make it easy to switch to. There also needs to be some more accounting code in place, so that we can actually use the Schedulers, whatever they happen to be called in the future. A whacky side note, it turns out that we totally need to ensure an object is loaded from the cache in order to delete it, we can't ensure that any references to other objects that are in the cache will be loaded otherwise.
2008-12-01	Wow, that's a lot of changes. You can use anything as a key now, as long as it	Mike Buland
	can be hashed. And we're about to test actually loading and saving persistant cache items. Fun.
2008-12-01	Woo! Very nearly there cache-wise, I'm about to change the name of the handler,	Mike Buland
	do a few more tests, and hopefully get something loading/saving.
2008-11-10	Ok, the cache-id officiation is being delegated to the CacheHandlers, this is	Mike Buland
	just fine, since they can do it any way they want. The Congo CacheHandlers will all have to be specialized versions of the generic ones, but they'll use all the general functionality, just make up IDs differently. It'll rock.
2008-10-09	More cache development. I'm going to have to switch from template functions to	Mike Buland
	functors. I like template functions a little more, but functors can be at least as fast. It won't be much of a change.
2008-10-08	Hey, more cachey goo!	Mike Buland