Re: AbstractSelectableChannel

> perhaps we should try a async emulation layer
> instead of using nio. 

I'm generally against any kind of emulation (except for testing code).
If it isn't built in the API/framework/implementation,
I generally reject code that performs extra backflips to 'workaround' a problem.
For us, here, it defeats the purpose of an asynchronous api in a seda environment (being
scalable).
(I presume all emulation layer have scalibility issues, which isn't far from thruth).


> There is a true async implementation from IBM that
> could solve the known problem of scalability (C10K
> problem).

Then I would leave it out of sandstorm, because sandstorm should be self contained and depend only
on JDK. People wanting such ibm lib are still allowed to code handlers for it. But sandstorm
doesn't have to promote it. I expect sandstorm programmers to be jdk limited at first. If jdk
doesn't offer proper async socket, then we can't either (unless you want the nbio stuff to be an
official lib - good luck with portability).



	
		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - You care about security. So do we. 
http://promotions.yahoo.com/new_mail


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/