On Wed, 2006-10-25 at 12:16 -0500, Timothy Brownawell wrote:
On Wed, 2006-10-25 at 11:24 -0500, Matthew A. Nicholson wrote:
You could have also used errno style error codes, although HTTP codes
are probably more widely known (maybe not).
Really, it's not just HTTP. There's also FTP and
Timothy Brownawell wrote:
Currently it uses these, somewhat based on the HTTP codes:
const static int no_error = 200;
const static int bad_request = 400;
const static int protocol_error = 401;
const static int permission_error = 403;
//const static int other_error = 500;
const
On Wed, 2006-10-25 at 11:24 -0500, Matthew A. Nicholson wrote:
Timothy Brownawell wrote:
Currently it uses these, somewhat based on the HTTP codes:
const static int no_error = 200;
const static int bad_request = 400;
const static int protocol_error = 401;
const static int
There's a new branch nvm.tbrownaw.netsync-note-hooks that changes the
note_netsync_* hooks slightly, as well as some supporting changes in
netsync.cc .
The most noticable change to the hooks is that note_netsync_start is now
called at the beginning of the connection, and that note_netsync_start
Just wanted to let you know that I have no problem with that change.
Actually, some of the new parameters would make certain things easier
for me :-).
In message [EMAIL PROTECTED] on Tue, 24 Oct 2006 15:16:23 -0500, Timothy
Brownawell [EMAIL PROTECTED] said:
tbrownaw There's a new branch
