On 28 Oct 2009 at 13:09, GrayHat wrote: [snip] > one I just suggested) in ClamD the developers should handle > two signatures "buffers" one containing the current ones which > will let the scanner work while the signatures are reloaded into > the second "buffer" at that point, and only at that point, the code > should apply a "lock", swap the buffers and discard the old one > but as you see it's not so easy to implement such a thing, while > adding support for a "BUSY" reply should be quite easy
Whether they eventually go for 2 buffers or similar is unknown, but I think they would be very reluctant to start changing the api with an extra reply after all the turmoil over the 0.95 release. paul ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
