On Thu, 26 Nov 2009, Peter Stuge wrote:
The thought that occured to me before was that we might need to take a bit
of a stand in libssh2 here on whether it should provide error codes that are
close to the protocol errors (which I would prefer) or whether it should try
to be smart and cook protocol error codes into something that could be
expected that application writers would prefer, or just where we think that
protocol errors suck.
Personally I rather like the protocol but on the other hand maybe it's too
low level sometimes?
In my experience, it is a gain in the long run to stay close to the
protocol(s) we work with and provide error codes that reflect what happened on
the protocol layer. IOW: I agree with Peter here.
We should of course document our error codes, and those descriptions should be
helpful for app authors to figure out what different codes mean and how they
can possibly act on them.
--
/ daniel.haxx.se
_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
