diff options
author | Mike Buland <eichlan@xagasoft.com> | 2007-10-14 22:27:51 +0000 |
---|---|---|
committer | Mike Buland <eichlan@xagasoft.com> | 2007-10-14 22:27:51 +0000 |
commit | e72d6077b475bc6142afc3b5967db113922c76f5 (patch) | |
tree | 45bdb7b69ec4c1dbcfadc1fa568b1d6b341a6f0f /src/protocolhttp.h | |
parent | 44eac9521632f8da42f73085db945bdba45f8311 (diff) | |
download | libbu++-e72d6077b475bc6142afc3b5967db113922c76f5.tar.gz libbu++-e72d6077b475bc6142afc3b5967db113922c76f5.tar.bz2 libbu++-e72d6077b475bc6142afc3b5967db113922c76f5.tar.xz libbu++-e72d6077b475bc6142afc3b5967db113922c76f5.zip |
Fixed an interesting ideosyncacy in Bu::Hash in a safe way, I should try to do
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.
Diffstat (limited to '')
-rw-r--r-- | src/protocolhttp.h | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/src/protocolhttp.h b/src/protocolhttp.h index e2612f5..85510e3 100644 --- a/src/protocolhttp.h +++ b/src/protocolhttp.h | |||
@@ -11,7 +11,14 @@ | |||
11 | namespace Bu | 11 | namespace Bu |
12 | { | 12 | { |
13 | /** | 13 | /** |
14 | * | 14 | * An HTTP Protocol handler. Yes, I know that HTTP stands for Hyper Text |
15 | * Transfer Protocol, and that the Protocol part is redundant, but in this | ||
16 | * case the word Protocol is refering to the Libbu++ construct Bu::Protocol, | ||
17 | * and not a means of encoding conversations. Anyway, this class represents | ||
18 | * a general HTTP server processor. Every time a request comes in it calls | ||
19 | * the onRequest function in a subclass with the method and URI that were | ||
20 | * requested. The sub-class can then do whatever it needs to to send back | ||
21 | * a response. | ||
15 | */ | 22 | */ |
16 | class ProtocolHttp : public Protocol | 23 | class ProtocolHttp : public Protocol |
17 | { | 24 | { |