Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
shinolajla1234
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
3 ms
·
1.
▲
PhillyETE Presentation: Future of the JVM
(emergingtech.chariotsolutions.com)
2 points
by
shinolajla1234
13y ago
|
0 comments
2.
▲
by
shinolajla1234
13y ago
With a thread pool shared by actors, even yours, if one of the actors fails, that thread is gone until the pool creates a new one (as needed). That's one less available thread until the recreation occurs. To minimize the impact on other a
3.
▲
by
shinolajla1234
13y ago
I agree that using selective receive helps in dealing with messages that arrive out of the order of a specific state transition. Akka gives users the ability to stash messages if they want to. On the JVM, a long-running actor-based applic
4.
▲
by
shinolajla1234
13y ago
If you're not replaying unhandled messages, you're not doing selective receive. To quote LYSEFGG, "Ignoring some messages to handle them later in the manner described above is the essence of selective receives" ( http://learnyousomeerlang.
5.
▲
by
shinolajla1234
13y ago
Selective Receive sounds great. Any idea how to handle messages that continue to pile up behind your actor when they're never handled? Do they get culled somehow after a period of time? If not, how do you handle the inherent memory leaking
6.
▲
by
shinolajla1234
14y ago
Akka does that as well, and you're right, it's very important for writing declarative, distributed logic. Akka's ActorRef abstracts over the physical location of the actor, just as Erlang's PIDs do.
7.
▲
by
shinolajla1234
14y ago
That's not entirely true. Erlang OTP allows for selective receive, and will stash unhandled messages to the side. When a received message is handled, all unhandled messages are retried because the actor may have changed what messages
8.
▲
by
shinolajla1234
14y ago
Ask @iamwarry on Twitter - Maxime Dantec did the site design. Talented fellow.
9.
▲
by
shinolajla1234
14y ago
Definitely. Drives me crazy when people are closed-minded about adopting the right technology to address a particular problem.
10.
▲
When Developers Are Afraid to Try Something New
(datamation.com)
5 points
by
shinolajla1234
14y ago
|
3 comments