1 Aug 2007 13:50
Re: Remote Actors
Thanks for your reply. For my current research, I'm trying to allow get dynamically generated actors to receive messages from the network. I was trying to achieve this by using message passing rather than some sort of external gateway/actor name server but it seems that I have little choice in the matter. In addition, I have my eye on researching migrating actors and was wondering if SCALA could handle such matters. Initially, I thought that simply sending an object, wrapping it, and then registering it on some remote node would work, but it doesn't look like the case. I'll do some more work on this, thanks for your help. Itay wrote: > > Brian, > > What are you trying to achieve? It seems to me that you either want to be > able to migrate actors across the network, which is not possible with the > current framework of actors (as far as I can see) unless you add a lot of > your own machinery, or that you are trying to be able to communicate > within your network about how to reach various actors. > > If it is the second one, my suggestion would be to have a known actor name > server (i.e. ANS), that has a known address and port (i.e. location), and > which you would send a request, say: > > ANS ! ActorLocation(someActorsName);(Continue reading)
What does "-Xgenerics" mean and when should I add this switch?
Stepan Koltsov-2 wrote:
>
> Try to compile without -Xgenerics?
>
> Seems like scala.collection.jcl is compiled without -Xgenerics at least in
> 2.5.
>
> --
> Stepan
>
>
RSS Feed