Within the JVM it’s dead easy to integrate between languages… :-) Random fact: I’ve actually used Scala code from JRuby on Rails some years ago. An outline on how to do this is on my blog: http://www.blog.project13.pl/index.php/fun/1497/teaching-jruby-talk-with-scala-on-rails/ And as you can see, it’s pretty easy, not sure if feasible nowadays though as Play is getting pretty good in the "developer productivity" area :-) (We did not end up using JRuby/Scala on Rails in the project I was working on (and went full Scala), by the way, but it was an interesting though short experiment).
Coming back to the questions though… in order for this to happen to (open up the cluster for “any language” client), we’ll need to re-think (?), stabilise, document and publish our remoting protocol, as well as (probably) change our serialisation format used. Such protocol would be accessible from any language – producing the bytes is the the one of the smaller problems actually, once we’d set on a serialisation format. There have been some rough ideas, but are currently focusing on tasks at hand (persistence, streams, akka-http etc). -- Konrad 'ktoso' Malawski hAkker @ typesafe http://akka.io -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
