Hi,
we are using Akka for a modular application where various modules provide
services. The application was initially developed without Akka. To support
multiprocessing, we added special modules that can send and receive data
using TCP / UDP.
The application now uses Akka, but we still use our old approach to send
data using TCP / UDP for multiprocessing.
Unfortunately this approach is a bit limited and it would be nice to make
it possible to use Akka remoting to run modules in several processes. As a
first step I tried to make sure all Props are serialize. To check this I
enabled
akka {
actor {
serialize-creators = on
}
}
But now I run into a problem: we have some modules that e.g. share a CORBA
connection (e.g. one module creates a CORBA connection and some other
modules use this connection to access services). Obviously a CORBA
connection is not serializable and I get an exception when I run the
application.
Is there some way to tell Akka for certain Actors that is it ok that props
are not serializable? The only thing I found is to set deploy.scope to
LocalScope. Can someone provide an example how to do this for certain
actors?
Is it acutally possible to address actors in application.conf not by path,
but by class or interface it implements? Then one could mark all actors
with props that are not serializable (by design) with that interface and
exclude them easily from serialize-creators checks.
Thanks,
Michael
--
>>>>>>>>>> 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.
