< Previous by Date	Date Index	Next by Date >
	Thread Index	Next in Thread >

[reSIProcate-users] virtual process() in SelectInterruptor?

From: "Mats Behre" <Mats.Behre@xxxxxxxxxx>
Date: Tue, 2 Dec 2008 15:18:45 +0100

Title: virtual process() in SelectInterruptor?

Hello,

We are running the reSIProcate stack through the InterruptableStackThread class. In order to signal the main thread when and only when there are new messages pending, I have changed the process function of SelectInterruptor to be virtual, and am using a subclass of it for the SipStack and InterruptableStackThread instances. (This subclass' version of process does our checks and then calls SelectInterruptor::process.)
Is this for some reason a bad thing to do? If not, could the change make it into the standard code base?

Mats

Follow-Ups:
- Re: [reSIProcate-users] virtual process() in SelectInterruptor?
  - From: Scott Godin

Prev by Date: Re: [reSIProcate-users] Linker errors when building library
Next by Date: Re: [reSIProcate-users] virtual process() in SelectInterruptor?
Previous by thread: Re: [reSIProcate-users] Linker errors when building library
Next by thread: Re: [reSIProcate-users] virtual process() in SelectInterruptor?
Index(es):
- Date
- Thread