[erlang-questions] Why is Erlang what it is?

[Kirill Zaborski]

BTW I have emailed Phillipp Haller (author of scala.actors). He responded
that version 1.0 is coming with some from of distributed transactions, web
services for actors, user manual and tutorial. It is expected the beggining
of the next year.

On 12/12/06, Jason Anderson <jla415@REDACTED> wrote:
>
> The api docs can be found at
> http://scala.epfl.ch/docu/files/api/index.html
>
> In particular you want to look at the scala.actors.remote.RemoteActorclass and the other classes in that package
>
> While functional and appearing to work with the few test cases I tried the
> current implementation of the RemoteActor probably should not be used as it
> will run at 100% cpu in a busy loop waiting for more data as long as there
> are jvms connected. You may wish to contact the author about this issue and
> to ask if there are any future plans for the library.
>
>
>
> On 12/12/06, Kirill Zaborski <qrilka@REDACTED> wrote:
> >
> > Where can I find some more details about it? E.g. how do you name JVMs
> > (like node names in Erlang)?
> > Are there any plans for more features?
> >
> > On 12/12/06, jla415 <jla415@REDACTED> wrote:
> > >
> > >
> > >
> > > Kirill Zaborski wrote:
> > > >
> > > > E.g. there are Scala actors library but it implements just one
> > > Erlang
> > > > feature of message-passing and as I see it's even not possible to
> > > send
> > > > messages between JVMs.
> > > > And of course we need the full power of OTP. But to implement it we
> > > need
> > > > "core" Erlang.
> > > >
> > >
> > > Somewhat off-topic here, but you can do message passing in the scala
> > > actors
> > > library between jvms with the scala.actor.remote.Actor.* classes,
> > > however
> > > the current implementation seems pretty inefficient as it basically
> > > does a
> > > while(inputStream.available() > 0) { ... } busy loop for each
> > > connection.
> > > Hopefully this will be fixed in the future to use NIO or similar async
> > > io
> > > techniques
> > >
> > > --
> > > View this message in context:
> > > http://www.nabble.com/-erlang-questions--Why-is-Erlang-what-it-is--tf2803978.html#a7830008
> > > Sent from the Erlang Questions mailing list archive at Nabble.com<http://nabble.com/>
> > > .
> > >
> > > _______________________________________________
> > > erlang-questions mailing list
> > > erlang-questions@REDACTED
> > > http://www.erlang.org/mailman/listinfo/erlang-questions
> > >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20061213/03684773/attachment.htm>