Yes,
we can use MINA, JETTY, GRIZZLY... but I think we need something lightweight, build into every Scala distribution. Dependency to other libraries will always be a problem. We need sth build in like RMI for Java and I beleive RemoteActor is for Scala.
What I thought is to create dedicated Selector implementation just for this one task : make RemoteActor NIO. Only one thread and thousands of connections. We don't need filters, coders/decoders, protocols...
What you think about that ?
Thanks,
Arthur.
Dnia 8 lipca 2009 13:58 Landei <
Daniel.Gronau@...> napisał(a):
>
>
>
> kermitas wrote:
> >
> > Hello,
> >
> > I just looked at Scala RemoteActor sources and I saw that implementation
> > is based on old fashion blocking IO.
> > Sicne this way a little bit old and (what is more important!) it is NOT
> > SCALABLE I wanted to ask if there are plans to make RemoteActors using NIO
> > ?
> >
> > In simple scenario when we build client-server software based on
> > RemoteActors we will kill machine after ~1000 connections. After reading
> > "Scala - the next five years" if we want Scala to be the language of the
> > future RemoteActors should be based on NIO !
> >
> > Thanks,
> > Arthur.
> >
> >
>
> I'm no expert, but I tend to agree. Maybe we could use existing
> infrastructure for this, e.g. things like
http://mina.apache.org/ ?
>
> Cheers,
> Daniel
>
> --
> View this message in context:
http://www.nabble.com/RemoteActor-based-on-NIO---tp24389820p24390172.html> Sent from the Scala - User mailing list archive at Nabble.com.
>
>
