| Age | Commit message (Collapse) | Author |
|---|
|
is the one I think should really be used pretty much of the time...
|
|
templatized containers.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
HttpGet is also much better now, and will timeout if it needs to.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ref-counting. You just have to be careful to not hand it an array...
|
|
|
|
|
|
particularly lame.
|
|
|
|
complain until I ran the tests. The tests will be fixed next.
|
|
ago.
|
|
|
|
|
|
|
|
|
|
really it does everything the old one did, does it better, easier, and possibly
faster.
|
|
and has more options. Use [] all you want!
|
|
|
|
sudden insperation and completely redid Hash. Now everything but delete is
implemented, including typesafe iterators and more. It's really cool, and
everyone should check it out and start using it right away!
|
|
used in general. The base unit, the confpair is a template, so if things go
right, you should be able to use this to store any kind of config data in a
nice and easily accessable way.
|
|
|
|
|
|
The connectionmanager no longer prints extra debugging.
|
|
|
|
|
|
|
|
|
|
|
|
and the connection monitor work in two-way-mode. Effectively you should be able
to write systems that both serve and initiate connections, and only write one
protocol.
|
|
you a Stream contianing the web server's response. Right now it doesn't parse
any headers or anything.
|
|
|
|
|
