List Info

Thread: Re: Unreal engine




Re: Unreal engine
country flaguser name
Sweden
2007-04-12 10:39:34
James Hague wrote:
> 
> "One game object per process" gets mentioned
> occasionally, and I think that's not as beautiful
> in practice as it sounds. 

I think you're right. There should of course be more
than one process per actor to start with. (:
I also like the suggestion I saw on LtU to have one
process per bullet...

Seriously, it's a bit like the telecoms analogy
"one process per phone call". We've actually
played with
lots of different models:
- one process per half-call
- process model following the H.248 model with context
  and terminations
- having just a context process per call, with the
  terminations handled as attributes, rather than 
  as separate processes.
- everything from one process for all calls to 
  10 processes per call.

There are pros and cons with each model, and which
one is best depends to some extent on what kinds of 
call we're talking about. SIP calls are much different
from ATM UNI point-to-point POTS calls, which are 
different from ATM PNNIR point-to-multipoint calls
(Mats C's absolute favourite.)

In short, you just have to take a deep dive into the
domain, and really understand the semantics, before 
you can come up with a good process model.

BR,
Ulf W

_______________________________________________
erlang-questions mailing list
erlang-questionserlang.org
http://www.erlang.org/mailman/listinfo/erlang-questions

Re: Unreal engine
user name
2007-04-12 11:12:25
> I think you're right. There should of course be more
> than one process per actor to start with. (:
> I also like the suggestion I saw on LtU to have one
> process per bullet...

I actually came to the same conclusion.  One process is the
simple
state machine.  One process is the master that handles
incoming
events.  For some state switches, the master tears down the
old state
machine process and creates a new one.

I still think that writing a DSL for the state machine
handling is the
way to go.  It makes the code a lot less sensitive to small
changes.

(On the flipside, it also makes sense to not use processes
at all for
simple objects, especially as game objects tend to advance
in
lock-step fashion.)
_______________________________________________
erlang-questions mailing list
erlang-questionserlang.org
http://www.erlang.org/mailman/listinfo/erlang-questions

[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )