[snmp] Possible flaw in transmitter?
Birgit Arkesteijn
birgit at westhawk.co.uk
Mon Feb 5 15:13:47 GMT 2007
I added Tim's code suggestion to Transmitter.interruptMe(), but didn't
test it.
The code is checked into cvs (on SF), see previous announcement.
Birgit
On Thu, Feb 01, 2007 at 10:28:11AM +0000, Tim Panton wrote:
> Andy, thanks,
>
> Yes, and I don't think it is strictly needed here.
>
> How about something as simple as:
> if( me!= null){
> me.interrupt();
> }
>
> If you follow Andy's case, then interrupt won't get called.
> That isn't a problem because all the interrupt does is to speed
> things up,
> the recv will timeout and the thread will clean itself up, just a bit
> later
> than it would have.
>
> I'll do some testing to see if this has any unpleasant side-effects,
> but
> it looks like the simplest solution, and one that won't slow down the
> vast majority of cases. (i.e. the _rare_ case is slower, but the rest
> not)
>
> Tim.
--
-- Birgit Arkesteijn, birgit at westhawk.co.uk,
-- Westhawk Ltd, Albion Wharf, 19 Albion Street, Manchester M1 5LN, UK
-- tel.: +44 (0)161 237 0660
-- <URL: http://www.westhawk.co.uk>
More information about the snmp
mailing list