On Fri, Feb 16, 2007 at 10:17:18AM -0500, Christopher X. Candreva said: > On Fri, 16 Feb 2007, Stephen Gran wrote: > > > What would be the point of having a socket ready before clamd is > > ready to do any work? Maybe I'm missing something. > > It would be something for other programs to connect to and wait for a > response, instead of generating a "socket does not exist" error.
So that they could potentially wait around until their internal timeout, instead of immediately returning? That really doesn't seem all that much like a win to me. I'd rather that the calling application was allowed to make an immediate decision (defer this mail, etc) than get stuck waiting waiting on a reply for an indeterminate amount of time. I grant you, it doesn't take clam all that long to load it's databases, but this idea you're advocating doesn't seem like very good application design to me. -- -------------------------------------------------------------------------- | Stephen Gran | Join in the new game that's sweeping | | [EMAIL PROTECTED] | the country. It's called | | http://www.lobefin.net/~steve | "Bureaucracy". Everybody stands in a | | | circle. The first person to do | | | anything loses. | --------------------------------------------------------------------------
signature.asc
Description: Digital signature
_______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
