Re: memcache(3) 1.2.0 released...

On Wed, 2005-01-12 at 17:58 -0800, John McCaskey wrote:
> On Wed, 2005-01-12 at 17:44 -0800, Sean Chittenden wrote:
[snip]
> > I'm going to include customized error handling in the next version, but 
> > not for the 1.2.0 series.  I'll roll out an updated release later 
> > tonight.  -sc
> > 
> 
> Is that to say you will roll out an updated 1.2.0 with the memory fixes,
> but that error handling is being put off? or you will roll out an
> updated 1.2.0 with the memory fixes, and a new version with error
> handling?
> 
> The error handling is neccesary for me, so I'm just trying to figure out
> whether I should add it myself, or wait for you to do so and save myself
> some time :)
> 

I'd also like to see all errx() calls removed and handled more
gracefully, for my use I've updated all of these to just err() and then
call mcm_server_deactivate() right after and return an error code.

It's unacceptable for a memcache error to cause my entire application to
exit unexpectedly.  No error could be serious enough for this as the
application can still function 100% (albeit with a big performance hit)
without the cache working at all.

I'm guessing you are probably in agreement, and just haven't gotten
around to adding better handling for these conditions yet?

-- 
John A. McCaskey
Software Development Engineer
Klir Technologies, Inc.
johnm@xxxxxxxx
206.902.2027