3 ms·
"parsing xml spin off a process so it can track state" Don't do that. Use state tracking data type. "the main process" That's not a thing in the BEAM. For
by throwawaymaths 3y ago
"parsing xml spin off a process so it can track state"
Don't do that. Use state tracking data type.
"the main process"
That's not a thing in the BEAM.
For something pure compute (i.e. no need for connection pools), if your user really needs that, then they can run the xml parsing in their own spawned process. Even if it's I/O bound, Erlang VM already makes great decisions about yielding, you will almost certainly not do better. You should not make concurrency decision on the users behalf.