--- In Jim Jackson <> wrote:
> Yes true. But if you want to get stuff off the board over the net, then ANY
> network destination can be unaccessible and so for any protocol/method
> you'd need a strategy to cope with that. And a full blown mail service
> daemon with queues etc just might be slightly over the top :-)
Agreed. One can spend a tremendous amount of time implementing code that deals
with unlikely-but-conceivable error states and trying to recover gracefully
from them, when sometimes it is best to just log the problem and move on*. I
suppose you just have to know your product -- e.g., the nuclear reactor
monitoring code warrants a lot more effort spent trying to get messages out
when something goes awry than does the webcam streaming code for the penguin
exhibit at the zoo.
* And hey, there's plenty of software out there that doesn't even check for or
log errors... :-)
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|