July 1997
- A simple political/social system? Jon A. Lambert
- A simple political/social system? clawrenc@cup.hp.com
- A simple political/social system? Marian Griffith
- A simple political/social system? clawrenc@cup.hp.com
- A simple political/social system? Jon A. Lambert
- Wounds and trauma Adam Wiggins
- Wounds and trauma clawrenc@cup.hp.com
- Wear Location System Jon A. Lambert
- Level abstractions clawrenc@cup.hp.com
- (fwd) Popularity of text-based MUDS clawrenc@cup.hp.com
- trying again Chris Gray
- My page, such as it is. Michael A. Hohensee
- What happened? Michael Hohensee
- Testing coder@ibm.net
- > Integrating PK Matt Chatterley
- Level abstractions / Game realism issues Matt Chatterley
- C&C and Event Rescheduling Shawn Halpenny
- C&C and Event Rescheduling clawrenc@cup.hp.com
- C&C and Event Rescheduling Shawn Halpenny
- C&C and Event Rescheduling clawrenc@cup.hp.com
- C&C and Event Rescheduling Shawn Halpenny
- C&C and Event Rescheduling clawrenc@cup.hp.com
- C&C and Event Rescheduling Shawn Halpenny
- C&C and Event Rescheduling clawrenc@cup.hp.com
- C&C and Event Rescheduling Shawn Halpenny
- C&C and Event Rescheduling Chris Gray
- C&C and Event Rescheduling Shawn Halpenny
- C&C and Event Rescheduling clawrenc@cup.hp.com
- C&C and Event Rescheduling Chris Gray
- C&C and Event Rescheduling clawrenc@cup.hp.com
- C&C and Event Rescheduling Shawn Halpenny
- C&C and Event Rescheduling clawrenc@cup.hp.com
- C&C and Event Rescheduling Jon A. Lambert
- C&C and Event Rescheduling clawrenc@cup.hp.com
- C&C and Event Rescheduling Jon A. Lambert
- C&C and Event Rescheduling Jon A. Lambert
- C&C and Event Rescheduling Shawn Halpenny
- C&C and Event Rescheduling clawrenc@cup.hp.com
- C&C and Event Rescheduling Nathan Yospe
- C&C and Event Rescheduling Adam Wiggins
- C&C and Event Rescheduling Richard Woolcock
- C&C and Event Rescheduling clawrenc@cup.hp.com
- C&C and Event Rescheduling Richard Woolcock
- C&C and Event Rescheduling clawrenc@cup.hp.com
- C&C and Event Rescheduling Adam Wiggins
- C&C and Event Rescheduling Marian Griffith
- C&C and Event Rescheduling clawrenc@cup.hp.com
- C&C and Event Rescheduling Adam Wiggins
- C&C and Event Rescheduling clawrenc@cup.hp.com
- C&C and Event Rescheduling Miroslav Silovic
- C&C and Event Rescheduling clawrenc@cup.hp.com
- C&C and Event Rescheduling Jon A. Lambert
- C&C and Event Rescheduling Shawn Halpenny
- C&C and Event Rescheduling Miroslav Silovic
- C&C and Event Rescheduling clawrenc@cup.hp.com
- C&C and Event Rescheduling Miroslav Silovic
- C&C and Event Rescheduling Miroslav Silovic
- C&C and Event Rescheduling clawrenc@cup.hp.com
In <199707311608.SAA00450@mare.zesoi.fer.hr>, on 07/31/97
at 07:12 PM, Miroslav Silovic <silovic@mare.zesoi.fer.hr> said:
>> In <199707261742.TAA00453@regoc.srce.hr>, on 07/26/97
>> at 10:53 AM, silovic@srce.hr (Miroslav Silovic) said:
>> commit as I do. This could allow a failed event to die and reschedule
>> much sooner than if it had to wait for the other contender to commit
>This was my intention.
To an extent however it could reduce responsiveness:
Very long event X starts processing.
Near the end of X's run: very short event Y starts processing.
Y locks resource A.
X requests A and dies.
Didn't you have some sort of age/priority scheme in there to counter
this? I seem to remember something such.
>> It also changes the character fo the DB accesses. In the lockless
>> model events compete to C&C successfully. Events with smaller
>> workings have an advantage at C&C time, as do events with shorter run
>> times. Its a question of who is in and out first. Neither of those
>> points are true for your model. For you, more or less, the first to
>> reach the base has it, holds it, and is guaranteed to commit
>> successfully (ignoring questions of needing to access an object which
>> another already has locked, which is not a safe assumption as below).
>I consider this a good thing. Remember, you have change_parents
>function in Cold. When you call it, it guarantees that the database
>will be consistant after termination.
FWLIW I have a similar call, but I don't guarantee consistancy.
Instead I rebuild the inheritance tree when an outdated object is
detected. This doesn't change the workload much -- it just spreads it
out over time.
>The problem is that it means
>that constructor/destructor pairs get called on /all/ descendants of
>the affected object.
Translation: You have an event with a HUGE working set which is almost
guaranteed to fail to C&C due to the large number of objects involved.
This is precisely why I don't rebuild everything in one swell foop.
Note: My approach also allow optimising for those cases where two
different inheritance changes affect the same object -- which while
perhaps not the most common case, it sorta cute.
>Adding a parent to the user object, in other
>words, will touch all the users. This means that such task has to run
>with VERY high priority (and in my scheme, I intend to knock the
>locks off the lower-priority tasks, precisely because of this). Now,
>this takes about 20-30 seconds on a LARGE db (say, 5,000 users), if
>the parent change is significant. This means that if lower-priority
>tasks could kill this at will, it'd take 5-10 minutes for it to grow
>high enough in priority to actually complete, according to your
>scheme.
Were I to do this sort of mass munging of the DB by a single event,
I'd have the event start at one of the higher priority levels --
potentially even at single-threaded mode. I can do that.
>In my scheme, it'd get max priority, and all threads in its
>way would restart, but it'd complete in reasonable time without
>affecting the game too much.
Which I can do as well by short-circuiting the priority level scheme.
I don't see a net win/lose where.
>IMO, the events roughly fall into two categories: database
>recompilation (change_parents is one such), and game events. I think
>that game events roughy take equal ammount of time, and giving
>priority to the shorter event is actually big potential problem: If
>events take 20 and 200 ms respectively, total processing, when 30 ms
>even is rescheduled, is 20+2*200 = 420 ms, instead of 220ms. On the
>other hand, database recompilations are so unpredictable that they're
>best run with high priority or atomically, simply because that way
>the probability that something will break is the lowest.
True. The problem with the lockless model is that performance
degrades almost geometrically as contention rises.
>> Another potential problem is that your locking model opens itself to
>> infinite loops about the Dining Philosophers problem. Without some
>> very interesting deadlock detection it is quite possible to have (say)
>> a minimal set of 3 events each of which attempts to lock various
>> objects and all of which get killed/rolled back because one of the
>> other two events already has the requested resource. Consider:
>>
>> Objects A, B and C,
>>
>> Events X, Y and Z.
>>
>> X locks A.
>>
>> Y locks B.
>>
>> Z locks C
>>
>> X attempts to lock B and dies.
>>
>> Y attempts to lock C and dies.
>>
>> X restarts and locks A.
>>
>> Z attempts to lock A and dies.
>>
>> Y restarts and locks B.
>>
>> X attempts to lock B and dies.
>>
>> Z restarts and locks C.
>>
>> Y attempts to lock C and dies.
>>
>> ...etc.
>>
>> This is a very simplistic case. Add many more events, and have each
>> event attempt to access more than one object (5? 10?) and it becomes
>> almost probable.
>Actually I intend to reschedule the tasks with random delays,
>precisely because of this (I believe this solution is standard).
>Deadlock is improbable, then, because sooner or later things will
>schedule in the right order, with proper pause between each.
Random rescheduling is a standard approach, however I wouldn't label
it a solution. You might like to do a simulation here. I suspect
you'll be surprised by the results. The problem of this approach is
that its incredibly sensitive to both the load and to range of the
random number generated.
Specific case: If the random generation varies by a value which is
generally far smaller than the specific contending events in question,
then they'll continue to contend for a long while. There are other
nasty cases (a simulation should show you most of the nasty ones).
I wonder if you're not going to need to profile the run-length of most
of your verbs and tailor (perhaps dynamically at runtime) your random
rescheduling to suit.
>> Aside: Its not distributable, well, not in any sane manner, whereas
>> the lockless model rolls out there pretty easily, especially if you
>> allow objects to migrate between DB servers.
>My method would support RPC model of distribution, with remote
>proxies...
This sounds a lot like Cool's model.
>...(Cold already supports proxy objects, but they are not all
>that useful without proper thread safety). For that matter, I'm still
>split between RPC and replication in choosing the right model for
>distribution. Replication bombs the bandwidth with flinging the
>objects around, while RPC needs to interchange several remote-call
>packets to do anything. On the other hand, replication would fare
>REALLY badly if two servers do intense manipulation of the same
>object for any length of time.
Unter originally took the replication model. Latter design
discussions that I've heard of spoke of doing RPC until a threshhold
value (balance of local calls to remote calls from specific target) at
which point the object would be moved to the preferential server.
--
J C Lawrence Internet: claw@null.net
(Contractor) Internet: coder@ibm.net
---------------(*) Internet: clawrenc@cup.hp.com
...Honorary Member Clan McFUD -- Teamer's Avenging Monolith... - C&C and Event Rescheduling Miroslav Silovic
- C&C and Event Rescheduling clawrenc@cup.hp.com
- C&C and Event Rescheduling clawrenc@cup.hp.com
- C&C and Event Rescheduling clawrenc@cup.hp.com
- C&C and Event Rescheduling Jon A. Lambert
- C&C and Event Rescheduling Shawn Halpenny
- C&C and Event Rescheduling Jeff Kesselman
- C&C and Event Rescheduling clawrenc@cup.hp.com
- C&C and Event Rescheduling Jeff Kesselman
- C&C and Event Rescheduling clawrenc@cup.hp.com
- C&C and Event Rescheduling Jeff Kesselman
- not about pk anymore Marian Griffith
- not about pk anymore Huibai
- not about pk anymore Matt Chatterley
- not about pk anymore clawrenc@cup.hp.com
- not about pk anymore Alex Oren
- not about pk anymore Matt Chatterley
- not about pk anymore clawrenc@cup.hp.com
- natural language parser (Output) Nathan Yospe
- Virtual Chemistry Matt Chatterley
- Virtual Chemistry Adam Wiggins
- Virtual Chemistry Jon A. Lambert
- Virtual Chemistry Matt Chatterley
- Virtual Chemistry Jon A. Lambert
- Virtual Chemistry Adam Wiggins
- Virtual Chemistry Jon A. Lambert
- Virtual Chemistry Matt Chatterley
- Virtual Chemistry Michael Hohensee
- Virtual Chemistry Matt Chatterley
- Virtual Chemistry Marian Griffith
- Virtual Chemistry Chris Gray
- Virtual Chemistry Marian Griffith
- Virtual Chemistry Chris Gray
- Virtual Chemistry Matt Chatterley
- Virtual Chemistry Chris Gray
- Virtual Chemistry Matt Chatterley
- Virtual Chemistry clawrenc@cup.hp.com
- Virtual Chemistry Matt Chatterley
- Virtual Chemistry Nathan Yospe
- Virtual Chemistry Matt Chatterley
- Virtual Chemistry Nathan Yospe
- Virtual Chemistry Matt Chatterley
- Virtual Chemistry Marian Griffith
- Virtual Chemistry Matt Chatterley
- Virtual Chemistry Marian Griffith
- Virtual Chemistry Matt Chatterley
- Virtual Chemistry Jon A. Lambert
- Virtual Chemistry Matt Chatterley
- Virtual Chemistry clawrenc@cup.hp.com
- Virtual Chemistry Matt Chatterley
- Virtual Chemistry clawrenc@cup.hp.com
- Virtual Chemistry Marian Griffith
- Virtual Chemistry Jon A. Lambert
- Virtual Chemistry Brandon Van Every
- Virtual Chemistry Jon A. Lambert
- Virtual Chemistry Huibai
- Virtual Chemistry Matt Chatterley
- Virtual Chemistry Matt Chatterley
- Virtual Chemistry Adam Wiggins
- Virtual Chemistry Huibai
- Virtual Chemistry Marian Griffith
- Virtual Chemistry clawrenc@cup.hp.com
- Combat Adam Wiggins
- Attn JCL: A scenario for you Alex Oren
- Combat messages Marian Griffith
- Combat messages Adam Wiggins
- Combat messages Martin Keegan
- Combat messages Matt Chatterley
- What about drugs? Nathan Yospe
- What about drugs? Adam Wiggins
- What about drugs? Jon A. Lambert
- What about drugs? Martin Keegan
- coord-based recap? Huibai
- coord-based recap? clawrenc@cup.hp.com
- Docs uploaded Chris Gray
- What are the elements of playabilty? clawrenc@cup.hp.com
- META: Making the list public? clawrenc@cup.hp.com
- META: Making the list public? Cynbe ru Taren
- META: Making the list public? coder@ibm.net
- META: Making the list public? Michael Hohensee
- META: Making the list public? Chris Gray
- META: Making the list public? clawrenc@cup.hp.com
- META: Making the list public? Brandon Gillespie
- META: Making the list public? clawrenc@cup.hp.com
- META: Making the list public? Michael Hohensee
- META: Making the list public? Brandon Gillespie
- META: Making the list public? Shawn Halpenny
- META: Making the list public? clawrenc@cup.hp.com
- META: Making the list public? Shawn Halpenny
- META: Making the list public? Alex Oren
- META: Making the list public? clawrenc@cup.hp.com
- META: Making the list public? Shawn Halpenny
- META: Making the list public? clawrenc@cup.hp.com
- META: Making the list public? Jon A. Lambert
- META: Making the list public? clawrenc@cup.hp.com
- META: Making the list public? Matt Chatterley
- META: Making the list public? clawrenc@cup.hp.com
- META: Making the list public? Huibai
- META: Making the list public? Martin Keegan
- META: Making the list public? clawrenc@cup.hp.com
- META: Making the list public? Marian Griffith
- META: Making the list public? Jon A. Lambert
- META: Making the list public? clawrenc@cup.hp.com
- META: Making the list public? clawrenc@cup.hp.com
- META: Making the list public? Shawn Halpenny
- META: Making the list public? clawrenc@cup.hp.com
- META: Making the list public? Matt Chatterley
- Longbows and such. Cynbe ru Taren
- R-trees &kin Cynbe ru Taren
- R-trees &kin Martin Keegan
- META: Making the list public? S001GMU@nova.wright.edu
- META: Making the list public? clawrenc@cup.hp.com
- META: C&C and Event Rescheduling clawrenc@cup.hp.com
- Source data on Crossbows clawrenc@cup.hp.com
- Source data on Crossbow Cynbe ru Taren
- Source data on Crossbow Matt Chatterley
- Source data on Crossbow Cynbe ru Taren
- Source data on Crossbow Matt Chatterley
- Source data on Crossbow clawrenc@cup.hp.com
- Source data on Crossbow Matt Chatterley
- Source data on Crossbow clawrenc@cup.hp.com
- Source data on Crossbow Matt Chatterley
- Source data on Crossbow Caliban Tiresias Darklock
- Source data on Crossbow Marian Griffith
- Source data on Crossbow clawrenc@cup.hp.com
- Source data on Crossbow Orion Henry
- Source data on Crossbow Cynbe ru Taren
- Source data on Crossbow Matt Chatterley
- Source data on Crossbow Michael Hohensee
- Source data on Crossbow Matt Chatterley
- Source data on Crossbow clawrenc@cup.hp.com
- Source data on Crossbow daggers@iquest.net
- Source data on Crossbow Rudy Neeser
- Source data on Crossbow Malcolm Tester II
- Source data on Crossbow Travis Casey
- Source data on Crossbow rayzam
- Source data on Crossbow Blane Bramble
- Source data on Crossbow Daniel Carruth
- Source data on Crossbow Michael Tresca
- Source data on Crossbow Bobby Martin
- Source data on Crossbow Christopher Kohnert
- Source data on Crossbow Bobby Martin
- Source data on Crossbow Christopher Kohnert
- Source data on Crossbow Dave Rickey
- Source data on Crossbow werda555@yahoo.com
- Source data on Crossbow Nathan Yospe
- Source data on Crossbow Travis Casey
- Source data on Crossbow Bobby Martin
- Source data on Crossbow Hans-Henrik Staerfeldt
- Source data on Crossbow Bobby Martin
- Source data on Crossbow Ben Tolputt
- Source data on Crossbow andy.wharton@ascentialsoftware.com
- Source data on Crossbow Skaei@aol.com
- Source data on Crossbow rayzam
- Public Archives (META: Making the list public?) Brandon Gillespie
- Socrates - A brief look at AI(?) Jon A. Lambert
- Evil coders from beyond the grave Matt Chatterley
- Evil coders from beyond the grave Orion Henry
- Evil coders from beyond the grave Matt Chatterley
- Evil coders from beyond the grave Chris Gray
- Evil coders from beyond the grave Matt Chatterley
- Evil coders from beyond the grave Adam Wiggins
- Evil coders from beyond the grave Matt Chatterley
- Graphical MUDs Michael Hohensee
- Graphical MUDs Cynbe ru Taren
- Graphical MUDs Michael Hohensee
- Graphical MUDs Shawn Halpenny
- Graphical MUDs clawrenc@cup.hp.com
- Graphical MUDs Chris Gray
- Brief bio Niklas Elmqvist
- Brief bio Martin Keegan
- Multi-threaded programming under Linux Greg Munt
- Multi-threaded programming under Linux Nathan Yospe
- Multi-threaded programming under Linux Cynbe ru Taren
- Multi-threaded programming under Linux S001GMU@nova.wright.edu
- Multi-threaded programming under Linux Chris Gray
- Multi-threaded programming under Linux Jeff Kesselman
- Multi-threaded programming under Linux Cynbe ru Taren
- Multi-threaded programming under Linux Orion Henry
- Multi-threaded programming under Linux Michael Hohensee
- Multi-threaded programming under Linux] Michael Hohensee
- Multi-threaded programming under Linux clawrenc@cup.hp.com
- Multi-threaded programming under Linux Jon A. Lambert
- Multi-threaded programming under Linux Nathan Yospe
- Multi-threaded programming under Linux Jon A. Lambert
- Multi-threaded programming under Linux Alex Oren
- Multi-threaded programming under Linux clawrenc@cup.hp.com
- Multi-threaded programming under Linux clawrenc@cup.hp.com
- (fwd) LP: How does it work? coder@ibm.net
- Collision detection coder@ibm.net
- OT: Multi-threaded programming under Linux coder@ibm.net
- Motivating people Greg Munt
- Motivating people Chris Gray
- Motivating people Huibai
- Motivating people clawrenc@cup.hp.com
- Motivating people Jon A. Lambert
- Motivating people Greg Munt
- Motivating people clawrenc@cup.hp.com
- Motivating people clawrenc@cup.hp.com
- OT: Multi-threaded programming under linux Orion Henry
- Graphic MUDS. Jeff Kesselman
- Graphic MUDS. Chris Gray
- Graphic MUDS. Jeff Kesselman
- Graphic MUDS. Chris Gray
- Graphic MUDS. Matt Chatterley
- Graphic MUDS. Adam Wiggins
- Graphic MUDS. Chris Gray
- Graphic MUDS. Michael Hohensee
- Graphic MUDS. Jon A. Lambert
- Graphic MUDS. clawrenc@cup.hp.com
- Graphic MUDS. Adam Wiggins
- Graphic MUDS. Martin Keegan
- Graphic MUDS. Adam Wiggins
- Graphic MUDS. clawrenc@cup.hp.com
- Graphic MUDS. Martin Keegan
- Graphic MUDS. Matt Chatterley
- Graphic MUDS. Jeff Kesselman
- Graphic MUDS. clawrenc@cup.hp.com
- Stories? Marian Griffith
- KaVir Nathaniel Blundell
- OT: Server Web Site Jon A. Lambert
- Recent mail delivery problems... clawrenc@cup.hp.com
- Mail not getting to the list coder@ibm.net
- Mail not getting to the list Caliban Tiresias Darklock
- Mail not getting to the list Jeff Kesselman
- Graphic MUDS/Ultima Online Koster, Raph
- Graphic MUDS/Ultima Online Adam Wiggins
- Graphic MUDS/Ultima Online Koster, Raph
- Graphic MUDS/Ultima Online Jeff Kesselman
- Graphic MUDS/Ultima Online Adam Wiggins
- Graphic MUDS/Ultima Online Matt Chatterley
- Graphic MUDS/Ultima Online Koster, Raph
- Graphic MUDS/Ultima Online Jeff Kesselman
- Graphic MUDS/Ultima Online clawrenc@cup.hp.com
- Graphic MUDS/Ultima Online Matt Chatterley
- Graphic MUDS/Ultima Online Adam Wiggins
- Graphic MUDS/Ultima Online Alex Oren
- Graphic MUDS/Ultima Online Matt Chatterley
- Graphic MUDS/Ultima Online clawrenc@cup.hp.com
- Graphic MUDS/Ultima Online Koster, Raph
- Graphic MUDS/Ultima Online clawrenc@cup.hp.com
- Graphic MUDS/Ultima Online clawrenc@cup.hp.com
- Graphic MUDS/Ultima Online Chris Gray
- Graphic MUDS/Ultima Online Richard Woolcock
- Graphic MUDS/Ultima Online Matt Chatterley
- Graphic MUDS/Ultima Online clawrenc@cup.hp.com
- Graphic MUDS/Ultima Online Matt Chatterley
- Graphic MUDS/Ultima Online clawrenc@cup.hp.com
- Graphic MUDS/Ultima Online Matt Chatterley
- Graphic MUDS/Ultima Online Chris Gray
- Graphic MUDS/Ultima Online Jeff Kesselman
- Graphic MUDS/Ultima Online Nathan Yospe
- Graphic MUDS/Ultima Online Matt Chatterley
- Graphic MUDS/Ultima Online clawrenc@cup.hp.com
- Graphic MUDS/Ultima Online Matt Chatterley
- Graphic MUDS/Ultima Online Richard Woolcock
- Graphic MUDS/Ultima Online Matt Chatterley
- Graphic MUDS/Ultima Online Jeff Kesselman
- Graphic MUDS/Ultima Online Matt Chatterley
- Graphic MUDS/Ultima Online Richard Woolcock
- Graphic MUDS/Ultima Online Nathan Yospe
- Graphic MUDS/Ultima Online clawrenc@cup.hp.com
- Graphic MUDS/Ultima Online Richard Woolcock
- Graphic MUDS/Ultima Online Nathan Yospe
- Graphic MUDS/Ultima Online Adam Wiggins
- Graphic MUDS/Ultima Online clawrenc@cup.hp.com
- Graphic MUDS/Ultima Online clawrenc@cup.hp.com
- Graphic MUDS/Ultima Online Matt Chatterley
- Graphic MUDS/Ultima Online Koster, Raph
- Graphic MUDS/Ultima Online Jeff Kesselman
- Graphic MUDS/Ultima Online Michael Hohensee
- Graphic MUDS/Ultima Online Adam Wiggins
- Graphic MUDS/Ultima Online Matt Chatterley
- Graphic MUDS/Ultima Online clawrenc@cup.hp.com
- Graphic MUDS/Ultima Online clawrenc@cup.hp.com
- Graphic MUDS/Ultima Online Matt Chatterley
- Graphic MUDS/Ultima Online clawrenc@cup.hp.com
- Graphic MUDS/Ultima Online clawrenc@cup.hp.com
- Graphic MUDS/Ultima Online Jeff Kesselman
- Graphic MUDS/Ultima Online Adam Wiggins
- Graphic MUDS/Ultima Online Jeff Kesselman
- Graphic MUDS/Ultima Online Adam Wiggins
- Graphic MUDS/Ultima Online Jeff Kesselman
- Graphic MUDS/Ultima Online clawrenc@cup.hp.com
- Graphic MUDS/Ultima Online clawrenc@cup.hp.com
- First Muds - newbie magic? Nathan Yospe
- First Muds - newbie magic? clawrenc@cup.hp.com
- First Muds - newbie magic? Martin Keegan
- Dynamic Descriptions Nathan Yospe
- Dynamic Descriptions Chris Gray
- Dynamic Descriptions Martin Keegan
- Dynamic Descriptions clawrenc@cup.hp.com
- Dynamic Descriptions Nathan Yospe
- Dynamic Descriptions Jeff Kesselman
- Dynamic Descriptions clawrenc@cup.hp.com
- Dynamic Descriptions Jeff Kesselman
- Persistant worlds, Dan Huibai
- Worlds VS Games, etc {was GMuds, UO} Nathan Yospe
- Worlds VS Games, etc {was GMuds, UO} Koster, Raph
- OT: NIS/AlterNIC and the DNS system Caliban Tiresias Darklock
- OT: Mail not getting to the list clawrenc@cup.hp.com
- OT: Mail not getting to the list clawrenc@cup.hp.com
- Persistance/stability Chris Gray
- Persistance/stability Miroslav Silovic
- Persistance/stability Matt Chatterley
- Persistance/stability clawrenc@cup.hp.com
- Persistance/stability Chris Gray
- Persistance/stability Brandon Gillespie
- Persistance/stability Adam Wiggins
- Persistance/stability Chris Gray
- Persistance/stability Adam Wiggins
- Tilting at the SimWindmill - was UO Jon A. Lambert
- DESIGN: The purpose of MUDding? coder@ibm.net
- DESIGN: The purpose of MUDding? Brandon Van Every
- DESIGN: The purpose of MUDding? Matt Chatterley
- DESIGN: The purpose of MUDding? Brandon Van Every
- DESIGN: The purpose of MUDding? Matt Chatterley
- DESIGN: The purpose of MUDding? clawrenc@cup.hp.com
- DESIGN: The purpose of MUDding? Matt Chatterley
- DESIGN: The purpose of MUDding? Jeff Kesselman
- DESIGN: The purpose of MUDding? Jeff Kesselman
- DESIGN: The purpose of MUDding? clawrenc@cup.hp.com
- DESIGN: The purpose of MUDding? clawrenc@cup.hp.com
- DESIGN: The purpose of MUDding? clawrenc@cup.hp.com