| Age | Commit message (Collapse) | Author |
|---|
|
this with the Bu::Archive next. Basically, there's one generic template
function that will convert anything that can safely cast to a uint32_t and that
supports direct comparisson, and doesn't have it's own override already to be
a Hash key, such as char, uint8_t, uint64_t, etc.
The Telnet protocol handler does everything I need it too for now, next up for
it is escape sequence handling, it would be nice to make this general too, by
using the termcap database or something, but there is an ANSI/ISO standard now,
I may just go ahead and use that. Also, it looks like it'd be pretty easy to
make the canonical mode editing functions be pluggable to facilitate different
types of editing, but that can be done down the road as well.
|
|
it just now. The Queue class has some obvious advantages over list if you
really only need Queue functionality, the main one being size, but also you can
get a slight speed advantage.
|
|
negotiation issues that plagued the earlier version, now I just have to
actually process data.
|
|
much data in thou outgoing buffer on a write and you need to wait. Instead
the write operation returns zero right now if that happens. It should be the
only case that it returns zero in when there are bytes to be written and an
exception is not triggered.
|
|
|
|
better. I'll have to check to make sure the rest of the system is still working
well, but so far it looks like it. Right now it allows pipelining and general
keep alive, but it doesn't check the keep-alive variable, it just always does
it. While this isn't a bad thing, it does go against the RFCs SHOULDs.
|
|
general Http handler working, the test for the moment, is Doxysrv, I'll probably
write a cute little stand-alone one in libbu++ later as a demo/test.
|
|
before you commit :-P
|
|
has been fixed, it now safely disconnects after emptying the Client's outgoing
buffer.
Added some more helpers to Bu::FString.
Added the beginings of ProtocolHttp using a new method for processing protocols
that's based more strongly on an NFA state machine, this makes sense, but I
never had the desire to actually try implementing it before. It's working
pretty well.
|
|
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.
|
|
|
|
get function can no longer change the Hash in any way.
|
|
|
|
|
|
|
|
|
|
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.
|
|
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.
|
|
socket, i.e. your address, not the client's address. That's not what I had
intended, but it'd be nice to have later. This is corrected now.
|
|
|
|
right now. Unfortunately it doesn't compile right now, if you want to build
this version, just delete array.
On the other hand, Bu::List now has enqueue/dequeue functions.
|
|
using system variables and special tokens, such as ~name and ~/...
I like this, and think that it's ample precedent for adding things like
format(), formatAppend(), and formatPrepend(), which would all rock.
|
|
the name of Bu::Hash::size() to Bu::Hash::getSize() to be consistant accross
the system.
|
|
(common in web addresses) was put in the middle of a property list, now it
doesn't get confused, it just complains bitterly and refuses to work.
|
|
including StopOnError and handling/reporting of external exceptions.
|
|
|
|
Also added more tests to the FString unit tests and switched the ParamProc to
using FString instead of std::string, this will break a few programs in very
minor ways, a few seconds each to fix, I'd say.
|
|
|
|
|
|
operators, but that's a minor issue.
|
|
really sure how that could happen easily.
|
|
the file class. This is probably a good idea anyway, but it feels like a silly
fix to another problem.
|
|
|
|
compile under OSX. So far, no problems with anything else, it looks like build
and nango both build without problems, libbu++ is truly becoming a full cross-
platform toolkit.
|
|
access it even after closing a socket to assist with proper accounting.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the right way.
|
|
now, but some more testing needs to be done.
|
|
|
|
|
|
|
|
|
