Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connecting Scala server-side actors and DomActors #2

Open
omidb opened this issue Sep 10, 2018 · 1 comment
Open

Connecting Scala server-side actors and DomActors #2

omidb opened this issue Sep 10, 2018 · 1 comment

Comments

@omidb
Copy link

omidb commented Sep 10, 2018

Hi,

Thanks for akka.js-dom. It looks like a promising project with a lot of potentials. I was wondering if it's possible to mix this with Scala actors in backend. Let's say in the "simple" timer example. Is it possible to write the DomActor in a Scala server-side (is there any binding?) in backend and then serve it as JS code like a module. If there are possibilities like that, then one can write an JVM actor that send messages to DomActor all in Scala with a shared codebase. I might be talking non-sense here :D but more general question is how can one mix akka.js-dom with Scala?

Thanks

@andreaTP
Copy link
Member

Hi, thanks for the input!
I think there are 2 point here:

  • akkajs-dom for Scala -> this probably I will do at some point in the future, help will be really appreciated :-)
  • Workers spawned in the server -> this is a strange request actually ... maybe I'm missing something but spawning DomActor in the backend add a lot of complexity (timeout - connection probes etc. etc.) that is not (at the moment) tackled by the framework.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants