[Home] [Groups] - Message: [Prev in Group] [Next in Group]
4590: CORBA, RMI, threads
[Full Header] [Plain Text]
From: s001gmu@nova.wright.edu
Newsgroups: nu.kanga.list.mud-dev
Date: Sun, 15 Feb 1998 15:04:58 -0500 (EST)
References: [1]
Organization: Kanga.Nu
On Sun, 15 Feb 1998 coder@ibm.net wrote:
>
> On 29/01/98 at 10:29 AM, s001gmu@nova.wright.edu said:
>
> >So, to reuse my schedule example, you could have several different calls
> >like so:
>
> > event_driver.schedule(new combat_event(real_to_game_time(t), attacker,
> > defender));
> > event_driver.schedule(new heal_event(real_to_game_time(t), target,
> > amount));
>
> I simplify all of this by not using a stack based architecture, but
> instead using message passing. An "event" then is merely a tuple of an
> objectID and a message to pass to that object,
'stack based architecture'? As I understand my system, and the
terminology surrounding it, I'm using a Queue (granted, very similar to a
stack)... Do I need to pull out my intro books and read them again? :)
> >etc. Each event class descended from the generic event has it's own
> >handle() method. You'll also want to have each descended event class's
> >constructors take arguments of pertinent data, as above. You can make
> >the inheretence tree as broad and deep as you like, depending on how you
> >choose to organize things.
>
> You also end up with a very very shallow and simple inheritance tree.
True. I don't have a problem with that. :) Simple is good, a lot of the
time.
-Greg