users@grizzly.java.net

RoundRobinConnectionDistributor why not distinguish ACCEPT operation from READ/WRITE operation?

From: yangjun2 <yangjun1120_at_gmail.com>
Date: Tue, 7 Jun 2011 19:32:44 -0700 (PDT)

    @Override
    public GrizzlyFuture<RegisterChannelResult> registerChannelAsync(
            final SelectableChannel channel, final int interestOps,
            final Object attachment,
            final CompletionHandler<RegisterChannelResult>
completionHandler)
            throws IOException {
        final SelectorRunner runner = getSelectorRunner();
        
        return transport.getSelectorHandler().registerChannelAsync(
                runner, channel, interestOps, attachment,
completionHandler);
    }
    
    private SelectorRunner getSelectorRunner() {
        final SelectorRunner[] runners = getTransportSelectorRunners();
        final int index = counter.getAndIncrement() % runners.length;
        
        return runners[index];
    }
}


When many client current connection, grizzly all SeclectorRunner process
ACCEPT operation , and not one could process READ/WRITE operation.
How to do it?

--
View this message in context: http://grizzly.1045725.n5.nabble.com/RoundRobinConnectionDistributor-why-not-distinguish-ACCEPT-operation-from-READ-WRITE-operation-tp4464523p4464523.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.