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

Age	Commit message (Collapse)	Author
2010-04-27	The Bu::Ito thread class has changed the rules on the run function. It no	Mike Buland
	longer returns anything, that's fine, it's in a class, but it also is protected now. That doesn't really effect child classes much, they can make run public, but I reccomend protected to avoid confusion.
2010-02-13	Added and updated the license info in all the source files, they still said	Mike Buland
	copyright 2007-2008.
2010-02-04	david - Made a build-M3 file for building to windows (mingw). This one ↵	David
	actually builds *.cpp, yay!... Although i took out Process, Plugger, and Regex... to be re-added later... also had to stubify a few more functions when compiling on WIN32.
2009-01-16	I...think that's a little better. Wow, function pointers in windows have a	Mike Buland
	lot of problems. This may require a little more research, but basically, you can't just call them inline wherever you'd like. I managed to get it to work by providing simple one line wrapper functions for each function we acquired as a pointer. Crazy mess. Anyway, it should load the library just once now, and Bu::Socket looks a little bit cleaner, but not a heck of a lot. I also added some more docs and removed the author references.
2008-04-28	Apparently there were a number of things that weren't strict ISO C++, the new	Mike Buland
	version of gcc complained about them, none of these changes will break backward compatibility, so I fixed them. I added more docs too, it seems.
2008-02-10	Huh, forgot to commit the rest of the updates/changes/etc for the new	Mike Buland
	sever/client-link system.
2008-02-07	Just updated the copyright date.	Mike Buland

2008-02-07	Wowee, I think all this new stuff works, Conduit I don't need now, so it's not	Mike Buland
	done yet. The Client class now supports a function called getLink() which returns a ClientLink object. This object may then be passed off to any other class and called to send messages to that client object. It is threadsafe if ItoServer is being used, and not for Server. Sending a message via a ClientLink calls the onMessage function on the assosiated protocol. Note that sending messages from within protocol event handlers or functions they call, while safe, may be slow and it's reccomended that you avoid this.
2007-11-15	david - adding license tag to the top of all header files	David

2007-10-03	Nothing about function. I added a bunch of docs and re-arranged a bunch of	Mike Buland
	the existing docs. Taking advantage of some of the cooler extra features of doxygen I've started writing extra how-to pages covering working with sections of the library. Also, I started grouping the classes by function so they show up on the Modules page together, very cute.
2007-09-11	Ok...forgot a couple of things. Bu::ItoServer now monitors all client	Mike Buland
	connections and actually cleans up behind them when they're all done. Seems important. It also will cleanup any lingering sockets that are laying around at destruction time, although right now unless you force-stop the server thread there is no way to interrupt it. That'll come in a bit.
2007-09-11	Everything seems to work with the new Bu::ItoServer class, it operates very,	Mike Buland
	very similarly to the Bu::Server class, except that every incoming connection gets it's own thread. This functionality may have to be tuned later, to allow for maintaining a pool of connections as an option, but this is fine for now.