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

Age	Commit message (Collapse)	Author
2009-01-09	Whoops! You can't fix a problem in server and forget about ItoServer! That's	Mike Buland
	just aweful! Well, he's not forgotten now.
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.
2008-02-07	Corrected a very rare race condition in Bu::ItoServer where there was a chance	Mike Buland
	that the client would disconnect so quickly that it would be cleaned up before it was properly accounted for. I apparently added something to MiniMacro a while ago...probably the end tags I think...
2007-11-15	Added liscense info at the front of many, many files. Debating the old files.	Mike Buland

2007-09-11	I just added a comment, don't ask...	Mike Buland

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.