<!-- MHonArc v2.4.4 -->
<!--X-Subject: Re: [MUD-Dev] C&C and Event Rescheduling -->
<!--X-From-R13: "Xba O. Znzoreg" <wyflfvapNvk.argpbz.pbz> -->
<!--X-Date: Tue, 16 Sep 1997 16:22:43 +0000 -->
<!--X-Message-Id: 199709161622.LAA01237@dfw-ix16.ix.netcom.com -->
<!--X-Content-Type: text/plain -->
<!--X-Reference: 199708171721.MAA14449@dfw-ix11.ix.netcom.com -->
<!--X-Reference: 199709122259.PAA11371#xsvr3,cup.hp.com -->
<!--X-Head-End-->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<title>MUD-Dev message, Re: [MUD-Dev] C&C and Event Rescheduling</title>
<!-- meta name="robots" content="noindex,nofollow" -->
<link rev="made" href="mailto:jlsysinc#ix,netcom.com">
</head>
<body background="/backgrounds/paperback.gif" bgcolor="#ffffff"
text="#000000" link="#0000FF" alink="#FF0000" vlink="#006000">
<font size="+4" color="#804040">
<strong><em>MUD-Dev<br>mailing list archive</em></strong>
</font>
<br>
[ <a href="../">Other Periods</a>
| <a href="../../">Other mailing lists</a>
| <a href="/search.php3">Search</a>
]
<br clear=all><hr>
<!--X-Body-Begin-->
<!--X-User-Header-->
<!--X-User-Header-End-->
<!--X-TopPNI-->
Date:
[ <a href="msg01226.html">Previous</a>
| <a href="msg01228.html">Next</a>
]
Thread:
[ <a href="msg01201.html">Previous</a>
| <a href="msg00482.html">Next</a>
]
Index:
[ <A HREF="author.html#01227">Author</A>
| <A HREF="#01227">Date</A>
| <A HREF="thread.html#01227">Thread</A>
]
<!--X-TopPNI-End-->
<!--X-MsgBody-->
<!--X-Subject-Header-Begin-->
<H1>Re: [MUD-Dev] C&C and Event Rescheduling</H1>
<HR>
<!--X-Subject-Header-End-->
<!--X-Head-of-Message-->
<UL>
<LI><em>To</em>: <A HREF="mailto:mud-dev#null,net">mud-dev#null,net</A></LI>
<LI><em>Subject</em>: Re: [MUD-Dev] C&C and Event Rescheduling</LI>
<LI><em>From</em>: "Jon A. Lambert" <<A HREF="mailto:jlsysinc#ix,netcom.com">jlsysinc#ix,netcom.com</A>></LI>
<LI><em>Date</em>: Tue, 16 Sep 1997 12:23:39 -4</LI>
<LI><em>Comments</em>: Authenticated sender is <jlsysinc#popd,ix.netcom.com></LI>
<LI><em>Reply-to</em>: <A HREF="mailto:jlsysinc#ix,netcom.com">jlsysinc#ix,netcom.com</A></LI>
</UL>
<!--X-Head-of-Message-End-->
<!--X-Head-Body-Sep-Begin-->
<HR>
<!--X-Head-Body-Sep-End-->
<!--X-Body-of-Message-->
<PRE>
On 12 Sep 97 at 16:04, clawrenc#cup,hp.com wrote:
> In <<A HREF="msg00640.html">199708171721.MAA14449#dfw-ix11,ix.netcom.com</A>>, on 08/17/97
> at 10:22 AM, "Jon A. Lambert" <jlsysinc#ix,netcom.com> said:
[snipped sample code]
> A greviously long quote, but needed I think.
>
> What determines if a method call will be made as a nested transaction,
> or as a seperate event?
Only that it is flagged (or not flagged) as an event method.
> The problem here is taht a method/transaction
> which may normally be considered logically atomic (move character to
> next room for example), may have logical dependencies in a specific
> event context (transactions which depend on correct order of
> processing of nested transactions).
>
> eg:
>
> "Move" is an event method as above.
> The code reads:
>
> Move (east);
> FillBucket (water);
> Move (east);
> EmptyBucket (Fire);
>
> Without each Move only being done and compleated prior to the next
> calls, the fire may or may not get doused.
Correct. Such a method might be coded, but correct or intended
execution is not guaranteed, since in calling "event" methods
within nested transactions demands that the programmer acknowledge
the asynchronous and independent nature of the called events.
Two solutions come to mind:
1) Copy the Move event code within the new move method. I can't
envision coding the above example. Which is really a macro-event
much like a player entering the commands:
east;fill bucket with water;east;empty bucket on fire
Such a macro command would never be considered atomic in my game.
Would such cases be exceptional enough that duplicating code is
sufficient? If it was not considered atomic in all(?) cases then
"Move" would not have been implemented as an event.
Although, I'm sure I will stumble onto other examples.
2) Allow polymorphic determination of which method to call.
event Move(20,east) or Move(east)
Requires some code restructing to avoid unneeded duplication. And
would need some work as I currently don't allow intra-class
polymorphic methods.
Note: Event rescheduling is explicit.
I realize I must also come up with a reasonable representation of the
dragon's dinner scenario. :)
--
Jon A. Lambert
If I'd known it was harmless, I would have killed it myself.
</PRE>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<HR>
<!--X-Follow-Ups-End-->
<!--X-References-->
<UL><LI><STRONG>References</STRONG>:
<UL>
<LI><STRONG><A NAME="00640" HREF="msg00640.html">[MUD-Dev] C&C and Event Rescheduling</A></STRONG>
<UL><LI><EM>From:</EM> "Jon A. Lambert" <jlsysinc#ix,netcom.com></LI></UL></LI>
<LI><STRONG><A NAME="01201" HREF="msg01201.html">Re: [MUD-Dev] C&C and Event Rescheduling</A></STRONG>
<UL><LI><EM>From:</EM> clawrenc#cup,hp.com</LI></UL></LI>
</UL></LI></UL>
<!--X-References-End-->
<!--X-BotPNI-->
<UL>
<LI>Prev by Date:
<STRONG><A HREF="msg01226.html">Re: [MUD-Dev] Affecting the world</A></STRONG>
</LI>
<LI>Next by Date:
<STRONG><A HREF="msg01228.html">Re: [MUD-Dev] PK again (was: Character evolution)</A></STRONG>
</LI>
<LI>Prev by thread:
<STRONG><A HREF="msg01201.html">Re: [MUD-Dev] C&C and Event Rescheduling</A></STRONG>
</LI>
<LI>Next by thread:
<STRONG><A HREF="msg00482.html">Re: [MUD-Dev] New to this mailing list</A></STRONG>
</LI>
<LI>Index(es):
<UL>
<LI><A HREF="index.html#01227"><STRONG>Date</STRONG></A></LI>
<LI><A HREF="thread.html#01227"><STRONG>Thread</STRONG></A></LI>
</UL>
</LI>
</UL>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
<ul><li>Thread context:
<BLOCKQUOTE><UL>
<LI><STRONG>Re: [MUD-Dev] C&C and Event Rescheduling</STRONG>, <EM>(continued)</EM>
<ul compact>
<ul compact>
<ul compact>
<ul compact>
<ul compact>
<ul compact>
<LI><strong><A NAME="00749" HREF="msg00749.html">Re: [MUD-Dev] C&C and Event Rescheduling</A></strong>,
clawrenc <a href="mailto:clawrenc#cup,hp.com">clawrenc#cup,hp.com</a>, Wed 27 Aug 1997, 00:24 GMT
</LI>
</ul>
</ul>
</ul>
</ul>
</ul>
<LI><strong><A NAME="00630" HREF="msg00630.html">[MUD-Dev] C&C and Event Rescheduling</A></strong>,
Jon A. Lambert <a href="mailto:jlsysinc#ix23,ix.netcom.com">jlsysinc#ix23,ix.netcom.com</a>, Sun 17 Aug 1997, 06:21 GMT
</LI>
<LI><strong><A NAME="00640" HREF="msg00640.html">[MUD-Dev] C&C and Event Rescheduling</A></strong>,
Jon A. Lambert <a href="mailto:jlsysinc#ix,netcom.com">jlsysinc#ix,netcom.com</a>, Sun 17 Aug 1997, 17:21 GMT
<UL>
<LI><strong><A NAME="01201" HREF="msg01201.html">Re: [MUD-Dev] C&C and Event Rescheduling</A></strong>,
clawrenc <a href="mailto:clawrenc#cup,hp.com">clawrenc#cup,hp.com</a>, Fri 12 Sep 1997, 23:01 GMT
<UL>
<LI><strong><A NAME="01227" HREF="msg01227.html">Re: [MUD-Dev] C&C and Event Rescheduling</A></strong>,
Jon A. Lambert <a href="mailto:jlsysinc#ix,netcom.com">jlsysinc#ix,netcom.com</a>, Tue 16 Sep 1997, 16:22 GMT
</LI>
</UL>
</LI>
</UL>
</LI>
</ul>
</LI>
<LI><strong><A NAME="00482" HREF="msg00482.html">Re: [MUD-Dev] New to this mailing list</A></strong>,
Chris Gray <a href="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">cg#ami-cg,GraySage.Edmonton.AB.CA</a>, Tue 12 Aug 1997, 06:06 GMT
<UL>
<LI><strong><A NAME="00487" HREF="msg00487.html">Re: [MUD-Dev] New to this mailing list</A></strong>,
Matt Chatterley <a href="mailto:root#mpc,dyn.ml.org">root#mpc,dyn.ml.org</a>, Tue 12 Aug 1997, 16:41 GMT
</LI>
<LI><strong><A NAME="00488" HREF="msg00488.html">Re: [MUD-Dev] New to this mailing list</A></strong>,
Richard Woolcock <a href="mailto:KaVir#dial,pipex.com">KaVir#dial,pipex.com</a>, Tue 12 Aug 1997, 17:18 GMT
</LI>
</UL>
</LI>
<LI><strong><A NAME="00465" HREF="msg00465.html">New to this mailing list</A></strong>,
Richard Woolcock <a href="mailto:KaVir#dial,pipex.com">KaVir#dial,pipex.com</a>, Mon 11 Aug 1997, 19:44 GMT
</LI>
</UL></BLOCKQUOTE>
</ul>
<hr>
<center>
[ <a href="../">Other Periods</a>
| <a href="../../">Other mailing lists</a>
| <a href="/search.php3">Search</a>
]
</center>
<hr>
</body>
</html>