| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
the Connection class so that it won't die horribly if you don't provide the
pointers to updatable memory for the amount of time not spent waiting for data
during a read.
Also fiddled with the http test, as you can see...nothing important.
|
|
will be named like that, make life easier.
|
|
|
|
that wants to send messages to a containing programlink.
Also fiddled with other things...aparently.
|
|
|
|
|
|
when shutting down...
|
|
disconnected flag has been set.
|
|
reason.
|
|
very much like the original one, but now using build. You will need the latest
build in order to build the tests.
|
|
be partially cross-linked to the node that was the root of the copy. Also fixed
a bug in the xmlfilewriter that should make it both faster, and not mess up %
style replacements.
|
|
|
|
there, but there might be later. 0 means death.
|
|
|
|
|
|
I need more anyway.
|
|
|
|
Later this should be fixed and another function should be added.
|
|
md5... it was using uninitialized data...
|
|
|
|
|
|
really are.
|
|
connection class, that reads at least n bytes in x seconds.
|
|
|
|
|
|
or work.
|
|
|
|
be.
|
|
|
|
build now, for a while, and don't actually work yet, so just don't use this
revision of libbu++.
|
|
|
|
|
|
|
