[repro-users] questirons about fdset built in process loop

["Neal Sidhwaney" <nealsid@xxxxxxxxx>]

Hi

We are registering an external transport that does not share the stack
process & select, i.e. shareStackProcessAndSelect() returns false.

It appears that the FDSET built during the application loop can be
empty, causing the assertion in the following sample code to return
-1:

        int err =
fdset.selectMilliSeconds(resipMin((int)stackUac.getTimeTillNextProcessMS(),
50));
        assert ( err != -1 );
        stackUac.process(fdset);

My question is, is the programming model provided in the sample code
not applicable when our own custom transports handle socket behavior
themselves(and happens to be the only transport registered)?

If the assertion is not meant to be there for my scenario, do we still
need the fdset processing for the asynchronous DNS query results?

Thanks!

Neal