[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    Re: KIO/KHTML Error Handling Update
From:       Hamish Rodda <meddie () yoyo ! cc ! monash ! edu ! au>
Date:       2002-01-29 8:58:16
[Download RAW message or body]

>On Saturday 26 January 2002 07:06 pm, Hamish Rodda wrote:
>> Can someone please clarify for me the following? Thanks.
>>
>> ERR_UNSUPPORTED_PROTOCOL
>> Does this mean that the protocol version of the server is not supported,
>> or that the server does not support the client's version of the protocol?
>
>It means that KDE does not support the protocol. E.g. "https" is not
> supported if you do not have SSL installed.

Ok.

>> I suggest adding ERR_SERVER_UNSUPPORTED_PROTOCOL to indicate the latter
>> (the webdav ioslave will activate this one).
>
>I think it might be better to add something like ERR_CUSTOM which would
> allow the slave to specify the whole message itself.

I think that's the point of ERR_SLAVE_DEFINED, so the question then becomes 
whether we should have a specific error code for "protocol error" or whether 
it's such a rare event that it is not useful.

>> Is there a difference between the following:
>>
>> ERR_CANNOT_OPEN_FOR_WRITING and ERR_WRITE_ACCESS_DENIED?
>
>The first one is slightly more generic. It's also less helpfull since it can
>be anything... (e.g. disk full, path does not exist, no access etc..)

Ok.

>> ERR_COULD_NOT_LISTEN and ERR_COULD_NOT_BIND?
>
>Appearantly used when calls to listen() or bind() fail.

Do any slaves listen() ?

>> ERR_COULD_NOT_CLOSEDIR gives an error message of "Could not terminate
>> listing" - does this mean that a listing was requested, then cancelled,
>> and the listing could not be terminated? I didn't document this one yet
>> because I don't understand it myself.
>
>This one sounds completely useless. Probably added by someone who checks all
>his memory allocations as well.

:)

Hamish
[prev in list] [next in list] [prev in thread] [next in thread]