>On Mon, 16 Sep 1996 18:31:46 +0200, adei@aztec.co.za (Fred Dei-Cont) wrote:
> :
>> Yupee, this is great...... <bg>
> :
>To make it fit, I would prefer more input (-;. I have some ideas,
>what are error/warning conditions, but I am sure others have some too.
>Especially yours are welcome, Fred!
>
Ok, ok... I pick up the ball.
Before I get stuck in the details let me explain the following: I use
vsoup for Mail and News. For my EMail needs I don't need a Mailer with all
the bells and whistles so 'Yarn' is OK for me. I very often attach rather
large documents which more often than not are tied-up with deadlines. If I
portion-out vsoup's connect time I find it in the order of 2/3 Mail and 1/3
News. The connect-time for news/day is in the order of 30 minutes.
If I loose messages or corrupt datas concerning my News activities it is
annoying but otherwise it has no great impact.....the same cannot be said
for my Mail activities. This is the main-reason why on top of my WISHLIST
is the item: Improved error/diagnostic codes. Granted, with a good script
one catches most potential disasters but not everybody is an expert in
script-writing and that includes me.
*soup*'s activity falls broadly into segments:
COMMUNICATION and FILE-MANIPULATIONS.
Both can report errors but I think it would be correct to say that without
communication there is no manipulation. This suggest to me something like:
Communication --> Error Code 1
Manipulation --> " " 3
IMHO, those are the real error situations.
'COMM' we could further break-down into:
no connection
connection interrupted
Wrong address, wrong protocol etc
Perhaps we can lump together the 'wrong address etc' with 'no connection'
and this would leave us with:
No connection --> Diagnostic Code 11
Connection interrupted --> " " 13
For 'FILE-MANIPULATION':
No replies ready for sending --> Diagnostic Code 31
No mail available for downloading --> " " 33
The 'no mail' is certainly more a diagnostic than an error condition and
is only of any real value in a script-routine.
'No reply' could in certain circumstances be useful as for example, if the
'reply.zip' got somehow damaged or corrupted.
These are in short(haha.. you must be kidding) my 2 cents worth on this
subject. I have no idea if in the computer fraternity a generally accepted
usage or implementation of error/diagnostic codes exists.
Now the case rests for me ;-). For how long? hmm
Regards
Fred
-- Fred Dei-Cont Fax:+27 21 461-8861 <adei@aztec.co.za> +27 21 26-1616 ________________________________________________