August 1998

• Affordances and social method (Was: Wired Jon A. Lambert
• (Fwd) **NOTICE REGARDING YOUR SEARCHLIGHT SOFTWARE** Jon A. Lambert
• • (Fwd) **NOTICE REGARDING YOUR SEARCHLIGHT SOFTWARE** John Bertoglio
  • • (Fwd) **NOTICE REGARDING YOUR SEARCHLIGHT SOFTWARE** Caliban Tiresias Darklock
• OT: BBSs, s001gmu@nova.wright.edu
• Ansii color, needing some specs and or pointer Jon A. Lambert
• • Ansii color, needing some specs and or pointer Caliban Tiresias Darklock
• (fwd) "Smart" monsters Nathan Fenenga Yospe
• Interesting poll Koster, Raph
• • Interesting poll John Bertoglio
• Milgram experiment (was WIRED: Kilers have more fun) Mike Sellers
• Implementing god. quzah
• • Implementing god. Adam J. Thornton
  • • Implementing god. J C Lawrence
    • • Implementing god. Adam J. Thornton
      • • Implementing god. Koster, Raph
        • • Implementing god. Adam J. Thornton
          • • Implementing god. Koster, Raph
        • Implementing god. J C Lawrence
        • • Implementing god. Marian Griffith
          • • Implementing god. Adam J. Thornton
            • • Implementing god. Andy Cink
• Blender: free version J C Lawrence
• Blender: free version J C Lawrence
• • Blender: free version Adam Wiggins
• UOL/Linux client URLs J C Lawrence
• Socket-Script: Socket-capabable script language and matching library J C Lawrence
• • Socket-Script: Socket-capabable script language and matching library Adam J. Thornton
  • • Socket-Script: Socket-capabable script language and matching library J C Lawrence
  • Socket-Script: Socket-capabable script language and matching library Chris Gray
  • Socket-Script: Socket-capabable script language and matching library Chris Gray
  • • Socket-Script: Socket-capabable script language and matching library Oliver Jowett
  • Socket-Script: Socket-capabable script language and matching library Adam J. Thornton
  • • Socket-Script: Socket-capabable script language and matching library Nathan F Yospe
    • • Socket-Script: Socket-capabable script language and matching library Adam J. Thornton
    • Socket-Script: Socket-capabable script language and matching library ##Make Nylander
    • • Socket-Script: Socket-capabable script language and matching library Adam J. Thornton
  • Socket-Script: Socket-capabable script language and matching library Ola Fosheim Grøstad
  • • Socket-Script: Socket-capabable script language and matching library J C Lawrence
• Why threading? (Was: Output Classification Notes) Ola Fosheim Grøstad
• • Why threading? (Was: Output Classification Notes) J C Lawrence
• Secrets of the Game Designers s001gmu@nova.wright.edu
• 3D World Models Leach, Brad BA
• • 3D World Models S. Patrick Gallaty
• Toba Java->C Adam J. Thornton
• [IDEAS] Starting from scratch Franklyn Colebrooke, Jr.
• • [IDEAS] Starting from scratch Adam J. Thornton
  • [IDEAS] Starting from scratch Hans-Henrik Staerfeldt
  • • [IDEAS] Starting from scratch Adam Wiggins
  • [IDEAS] Starting from scratch Leach, Brad BA
  • • [IDEAS] Starting from scratch T. Alexander Popiel
    • [IDEAS] Starting from scratch Adam Wiggins
    • [IDEAS] Starting from scratch J C Lawrence
  • [IDEAS] Starting from scratch Ross Nicoll
  • • [IDEAS] Starting from scratch T. Alexander Popiel
    • • [IDEAS] Starting from scratch Holly Sommer
      • • [IDEAS] Starting from scratch T. Alexander Popiel
        • • [IDEAS] Starting from scratch Nathan F Yospe
          • [IDEAS] Starting from scratch Holly Sommer
          • • [IDEAS] Starting from scratch T. Alexander Popiel
    • [IDEAS] Starting from scratch s001gmu@nova.wright.edu
    • [IDEAS] Starting from scratch Matt Chatterley
  • [IDEAS] Starting from scratch Ross Nicoll
  • [IDEAS] Starting from scratch Ross Nicoll
  • [IDEAS] Starting from scratch Ross Nicoll
  • • [IDEAS] Starting from scratch J C Lawrence
  • [IDEAS] Starting from scratch J C Lawrence
  • • [IDEAS] Starting from scratch Adam Wiggins
• Question regarding Java threads Jon A. Lambert
• • Question regarding Java threads Chris Gray
  • • Question regarding Java threads Vadim Tkachenko
    • • Question regarding Java threads Ben Greear
    • Question regarding Java threads J C Lawrence
  • Question regarding Java threads Ben Greear
  • • Question regarding Java threads Jon A. Lambert
  • Question regarding Java threads Chris Gray
  • Question regarding Java threads Matt Chatterley
  • • Question regarding Java threads Ben Greear
• Protocols Vadim Tkachenko
• Events s001gmu@nova.wright.edu
• after the plague: mud report S. Patrick Gallaty
• • after the plague: mud report quzah
  • • after the plague: mud report Adam Wiggins
    • after the plague: mud report Ling
• Object Storage Fact Book, Release 4.0 (fwd) Nathan F Yospe
• Affordances and social method (Was: Wire d Magazine...) J C Lawrence
• META: List combat character and racial memory (was Re: J C Lawrence
• • META: List combat character and racial memory (was Re: kamikaze@kuoi.asui.uidaho.edu
  • • META: List combat character and racial memory (was Re: J C Lawrence
• Black Isle's Baldur's Gate J C Lawrence
• • Black Isle's Baldur's Gate Koster, Raph
  • Black Isle's Baldur's Gate Chris Gray
  • Black Isle's Baldur's Gate Koster, Raph
• 208.240.161.41 Adam J. Thornton
• • 208.240.161.41 Vadim Tkachenko
• ADMIN: Advertising on MUD-Dev J C Lawrence
• • ADMIN: Advertising on MUD-Dev Chris Gray
  • • ADMIN: Advertising on MUD-Dev Caliban Tiresias Darklock
    • • ADMIN: Advertising on MUD-Dev Ola Fosheim Grøstad
      • ADMIN: Advertising on MUD-Dev J C Lawrence
    • ADMIN: Advertising on MUD-Dev Vadim Tkachenko
    • • ADMIN: Advertising on MUD-Dev Adam Wiggins
      • • ADMIN: Advertising on MUD-Dev Robert Woods
        • ADMIN: Advertising on MUD-Dev Richard Woolcock
        • • ADMIN: Advertising on MUD-Dev Jeroen Ruigrok/Asmodai
          • • ADMIN: Advertising on MUD-Dev quzah
            • ADMIN: Advertising on MUD-Dev Richard Woolcock
            • • ADMIN: Advertising on MUD-Dev Jeroen Ruigrok/Asmodai
  • ADMIN: Advertising on MUD-Dev T. Alexander Popiel
  • ADMIN: Advertising on MUD-Dev Mike Sellers
  • • ADMIN: Advertising on MUD-Dev J C Lawrence
  • ADMIN: Advertising on MUD-Dev Michael Hohensee
  • • ADMIN: Advertising on MUD-Dev s001gmu@nova.wright.edu
    • • ADMIN: Advertising on MUD-Dev J C Lawrence
      • • ADMIN: Advertising on MUD-Dev quzah
        • ADMIN: Advertising on MUD-Dev John Bertoglio
      • ADMIN: Advertising on MUD-Dev Caliban Tiresias Darklock
      • ADMIN: Advertising on MUD-Dev quzah
      • • ADMIN: Advertising on MUD-Dev Caliban Tiresias Darklock
        • • ADMIN: Advertising on MUD-Dev s001gmu@nova.wright.edu
  • ADMIN: Advertising on MUD-Dev Chris Gray
  • ADMIN: Advertising on MUD-Dev Scatter
  • ADMIN: Advertising on MUD-Dev J C Lawrence
• Adverts in email on the list. Ben Greear
• • Adverts in email on the list. quzah
  • • Adverts in email on the list. Jon A. Lambert
    • • Adverts in email on the list. quzah
  • Adverts in email on the list. Holly Sommer
  • • Adverts in email on the list. Vadim Tkachenko
• Ethernet NICS, maximum connections..mud testing. Ben Greear
• • Ethernet NICS, maximum connections..mud testing. Vadim Tkachenko
• Ethernet NICS, maximum connections..mud testing. Ben Greear
• Ethernet NICS, maximum connections..mud testing. Chris Gray
• • Ethernet NICS, maximum connections..mud testing. Ben Greear
• lurker emerges James Wilson
  hello, I've been perusing some of your fascinating archives for a little
  while and thought I'd add my two cents (or maybe more than that). I sent a
  similar message a day or so ago, not noticing the big bold message in the
  list policy that told me I couldn't post yet, so that message is lost in
  /dev/null. Duh. Fortunately I have had the opportunity to do a little more
  research on what I want to talk about. I have been puttering around with mud
  development for years, and keep going around and around on the same
  questions. Here are two of them, in a hopefully-not-too-blathery degree of
  verbosity.
  
  my first issue is basic server control flow: select() vs. threading vs...?
  There are some startling numbers at the thttpd web site (<url:
  http://www.acme.com/software/thttpd>) showing the vast difference between
  single-threaded, select()-based http servers and servers based on other
  models (using one-thread-per-connection or a thread pool). This was a bit of
  a shock to me as I am quite enamored of threading (probably more because of
  its challenges than because of its necessity, I am forced to admit). I am
  curious as to what approaches the list readers feel are tenable, and what
  their pros and cons are.
  
  As I see it, not having gone the whole nine and tested it out, using a
  single, select()ing thread to do all your stuff would work fine if each
  operation is bounded by some small
  amount of time. That is, if you spend too much time in processing the
  received action,
  your responsiveness to pending requests goes down. I'm not sure how or if
  this issue is solved in the select()-based http servers, and am looking at
  the source code to try to suss it out. How do they deal with a request for a
  bigass file? Do all the ripe sockets wait to be select()ed while the bigass
  file is sent on its merry way? News at 11.
  
  One compromise which occurs to me is to make a sort of hybrid thread pool,
  where all the input comes through one thread and gets thrown at a group of
  worker threads that
  do the actual processing and send responses directly back to the user. That
  way, one
  can allow the input thread to go directly back to listening while processing
  of possibly indefinite duration goes on in other threads. In a similar way
  one could factor out the database magic, and so on. I'm not sure whether
  such variations would be any better than the standard thread-pool server.
  
  The second big issue I am interested in getting some expert opinions on is
  the mechanics of interaction between the threading system (assuming one is
  used), the heap (or database), and the internal logic of the mud, perhaps
  including user-scripted behaviors. That is, when one introduces threading
  into a persistent database system, a number of issues present themselves.
  Garbage collection, for instance, becomes a fascinating problem (see <URL:
  http://www.cs.utexas.edu/users/oops/papers.html#allocsrv>, at the UTexas
  site which also contains the Texas persistent store), while avoiding race
  conditions and deadlocks in code-that-used-to-work-dammit becomes a
  hairpuller. On top of those
  problems (soluble given a careful programming technique) one must protect
  the users
  from the horrors of synchronization, for their own sanity and for the
  stability of the whole
  system. However, removing synchronization from user-scripting implies that
  user scripts are either serialized or their correctness is otherwise assured
  using some other, more subtle mechanism.
  
  The simplest way of serializing mud processes would be to lock the database
  and heap of in-memory mud objects for every transaction. It seems to me this
  would reduce the system to one essentially identical to the single-threaded
  select() server. The lockless system described in the FAQ could be an
  improvement on this. In this system, access to the database is atomic, while
  in-memory objects are thread-local and competing modifications get resolved
  with a repeat of the modifying event. This pushes the serialization to
  different places, namely the point at which the database is read to generate
  the local copies and the point at which the database is written and checked
  for discrepancies. This is still an improvement because the lockless system
  allows concurrent processing once objects have been read in from the
  database. (I am still a little fuzzy on some details - how is the collection
  of objects to 'clone' determined? Does the cloning thread save two clones
  of the object, one 'as it was read in', and one 'production copy'? If not,
  how does it know the difference between the object's state-at-snapshot and
  the object's current database state (which might reflect modifications by
  other threads)? If a thread grabs an object and runs for a long time, will
  it see modifications to that object, or work with the old copy?)
  
  Another option which has occurred to me is to serialize groups of related
  objects which have a high probability of being accessed together, such as
  geographically proximate locations. Threads could then enjoy unrestricted,
  unlocked access to those 'local' objects. Access to non-local objects would
  have to be proxied through an event-passing mechanism; that is, in order to
  access object O in locale D, one would have to figure out that O lives in D
  and send a transaction T to D which could then be executed in a thread with
  exclusive access to D. The result of T could be the transmission of a
  followup transaction back to T's sender, and so on. All this overhead could
  bring a server to its knees if done improperly, and if non-local operations
  are frequent. Moreover objects would have to be disciplined so they don't
  hold onto references to non-local objects; a reference to a local object
  could then become illegal if that object moved. This seems problematic.
  Access to local objects could of course be proxied as well through
  transactions on the locale, but I find it doubtful that such a system could
  be efficient; you'd need a transaction for every read of every field. And if
  one uses transactions for everything, why not simply move to a
  single-threaded system that simulates threads using self-regenerating
  events?
  
  James
• • lurker emerges Chris Gray
  • • lurker emerges Adam J. Thornton
  • lurker emerges Chris Gray
  • lurker emerges Petri Virkkula
  • • lurker emerges T. Alexander Popiel
    • • lurker emerges James Wilson
      • • lurker emerges T. Alexander Popiel
      • lurker emerges Vadim Tkachenko
      • • lurker emerges Ben Greear
        • • lurker emerges J C Lawrence
        • lurker emerges T. Alexander Popiel
        • • lurker emerges Vadim Tkachenko
          • • lurker emerges T. Alexander Popiel
            • • lurker emerges Vadim Tkachenko
              • • lurker emerges T. Alexander Popiel
                • • lurker emerges Vadim Tkachenko
                  • • lurker emerges T. Alexander Popiel
                    • • lurker emerges Vadim Tkachenko
                • lurker emerges Vadim Tkachenko
  • lurker emerges Chris Gray
  • • lurker emerges Vadim Tkachenko
    • lurker emerges J C Lawrence
  • lurker emerges Petri Virkkula
  • lurker emerges J C Lawrence
  • lurker emerges Petri Virkkula
  • lurker emerges Chris Gray
  • • lurker emerges J C Lawrence
• Adverts in email on the list. Chris Gray
• • Adverts in email on the list. quzah
• Fw: lurker emerges James Wilson
• • Fw: lurker emerges T. Alexander Popiel
• Ethernet NICS, maximum connections..mud testing. Chris Gray
• • Ethernet NICS, maximum connections..mud testing. Ben Greear
• Ethernet NICS, maximum connections..mud testing. Chris Gray
• • Ethernet NICS, maximum connections..mud testing. Ben Greear
• Neat surrealistic graphical mudclients in Java? Ola Fosheim Grøstad
• Ethernet NICS, maximum connections..mud testing. Chris Gray
• • Ethernet NICS, maximum connections..mud testing. J C Lawrence
  • • Ethernet NICS, maximum connections..mud testing. Adam J. Thornton
  • Ethernet NICS, maximum connections..mud testing. Ben Greear
• META/ADMIN: ADMIN: Advertising on MUD-Dev Mike Sellers
• • META/ADMIN: ADMIN: Advertising on MUD-Dev Ola Fosheim Grøstad
• Rule #3 S. Patrick Gallaty
• OT: Ethernet NICS, maximum connections..mud testing. Shawn Halpenny
• • OT: Ethernet NICS, maximum connections..mud testing. Vadim Tkachenko
• META: List combat character and racial memory (was Re: Chris Gray
• List of rules suggestionbox Hans-Henrik Staerfeldt
• • List of rules suggestionbox Caliban Tiresias Darklock
• async i/o and threads (was: lurker emerges) James Wilson
• • async i/o and threads (was: lurker emerges Jon A. Lambert
  • • async i/o and threads (was: lurker emerges James Wilson
    • • async i/o and threads (was: lurker emerges Jon A. Lambert
• Amoeba: Distributed OS release J C Lawrence
• clients anyone?... Andrew Wilson
• • clients anyone?... Adam J. Thornton
  • • clients anyone?... Andrew Wilson
    • clients anyone?... Hans-Henrik Staerfeldt
    • • clients anyone?... Adam J. Thornton
      • clients anyone?... Bruce Mitchener, Jr.
      • • clients anyone?... James Wilson
        • clients anyone?... Adam J. Thornton
        • • clients anyone?... Andrew Wilson
          • • clients anyone?... Adam J. Thornton
            • • clients anyone?... Andrew Wilson
              • • clients anyone?... Adam J. Thornton
      • clients anyone?... Adam Wiggins
    • clients anyone?... Andrew Wilson
  • clients anyone?... J C Lawrence
  • • clients anyone?... Andrew Wilson
• Re:Methods to Reduce Ecological Wipeout Michael.Willey@abnamro.com
• ADMIN: Over quoting (again) J C Lawrence
• JASSS: The Journal of Artificial Societies and Social Simulation J C Lawrence
• Methods to Reduce Ecological Wipeout Leach, Brad BA
• • Methods to Reduce Ecological Wipeout s001gmu@nova.wright.edu
  • • Methods to Reduce Ecological Wipeout quzah
    • • Methods to Reduce Ecological Wipeout Michael.Willey@abnamro.com
  • Methods to Reduce Ecological Wipeout Koster, Raph
  • • Methods to Reduce Ecological Wipeout Michael.Willey@abnamro.com
    • • Methods to Reduce Ecological Wipeout Koster, Raph
      • • Methods to Reduce Ecological Wipeout Brandon J. Rickman
        • • Methods to Reduce Ecological Wipeout quzah
          • Methods to Reduce Ecological Wipeout Marian Griffith
        • Methods to Reduce Ecological Wipeout Damion Schubert
        • Methods to Reduce Ecological Wipeout J C Lawrence
    • Methods to Reduce Ecological Wipeout J C Lawrence
• LinuxThreads and SIGUSR1 (Ref: [MUD-Dev]) Adam J. Thornton
• Eye movement. quzah
• • Eye movement. James Wilson
  • • Eye movement. quzah
    • • Eye movement. S. Patrick Gallaty
      • • Eye movement. T. Alexander Popiel
    • Eye movement. Hans-Henrik Staerfeldt
• OGR: Ion Storm's Witchboy talks about the functionality of enemy AI. J C Lawrence
• • OGR: Ion Storm's Witchboy talks about the functionality of enemy AI. s001gmu@nova.wright.edu
  • • OGR: Ion Storm's Witchboy talks about the functionality of enemy AI. J C Lawrence
• Methods to Reduce Ecological Wipeout (fwd) Marc Hernandez
• avoiding ecological wipeout Laurel Fan
• Passing file descriptors to other processes Adam J. Thornton
• Yet another update on threads and signals Adam J. Thornton
• • Yet another update on threads and signals s001gmu@nova.wright.edu
  • Yet another update on threads and signals Chris Gray
  • • Yet another update on threads and signals Adam J. Thornton
  • Yet another update on threads and signals Chris Gray
  • • Yet another update on threads and signals Adam J. Thornton
  • Yet another update on threads and signals Chris Gray
  • • Yet another update on threads and signals Adam J. Thornton
• OT: access s001gmu@nova.wright.edu
• Affordances and social method cat
• Affordances and social method cat
• • Affordances and social method Caliban Tiresias Darklock
  • • Affordances and social method Ola Fosheim Grøstad
• Missing MUD-Dev post (fwd) Dr. Cat
• FW: UBE/high: W IRED: Kilers have more fun Koster, Raph
• Affordances and social method Koster, Raph
• Marian's Tailor Problem Koster, Raph
• • Marian's Tailor Problem Brandon Cline
  • Marian's Tailor Problem Hans-Henrik Staerfeldt
  • • Marian's Tailor Problem Brandon Cline
    • • Marian's Tailor Problem Ola Fosheim Grøstad
      • Marian's Tailor Problem Damion Schubert
  • Marian's Tailor Problem Chris Gray
• UBE/high: W IRED: Kilers have more fun Koster, Raph
• • UBE/high: W IRED: Kilers have more fun Mike Sellers
  • UBE/high: W IRED: Kilers have more fun s001gmu@nova.wright.edu
  • UBE/high: W IRED: Kilers have more fun Marian Griffith
• Question for the list (Semi-OT) Nathan F Yospe
• • Question for the list (Semi-OT) Oliver Jowett
  • • Question for the list (Semi-OT) Jon Leonard
  • Question for the list (Semi-OT) Ben Greear
• FW: UBE/high: W IRED: Kilers have more fun Jon A. Lambert
• Private Affordances and social method Mike Sellers
• • Private Affordances and social method Marian Griffith
  • • Private Affordances and social method Mike Sellers
• FW: UBE/high: W IRED: Kilers have more fun Marian Griffith
• UBE/high: FW: UBE/high: W IRED: Kilers have more fun Dr. Cat
• • UBE/high: FW: UBE/high: W IRED: Kilers have more fun S. Patrick Gallaty
• free XML Parser (was clients anyone?...) James Wilson
• UBE/high: FW: UBE/high: W IRED: Kilers Jon A. Lambert
• • UBE/high: FW: UBE/high: W IRED: Kilers Koster, Raph
  • • UBE/high: FW: UBE/high: W IRED: Kilers S. Patrick Gallaty
    • UBE/high: FW: UBE/high: W IRED: Kilers quzah
    • • UBE/high: FW: UBE/high: W IRED: Kilers James Wilson
      • UBE/high: FW: UBE/high: W IRED: Kilers Damion Schubert
    • UBE/high: FW: UBE/high: W IRED: Kilers J C Lawrence
• UBE/high: UBE/high: FW: UBE/high: W IRED: Kilers Dr. Cat
• Marion's Tailor Problem s001gmu@nova.wright.edu
• • Marion's Tailor Problem Caliban Tiresias Darklock
  • • Marion's Tailor Problem jwilson@rochester.rr.com
    • Marion's Tailor Problem Travis Casey
    • • Marion's Tailor Problem Caliban Tiresias Darklock
      • • Marion's Tailor Problem Adam J. Thornton
        • Marion's Tailor Problem Travis S. Casey
  • Marion's Tailor Problem Jynx {Wyrm / Tygr / Myth} Ryn
  • • Marion's Tailor Problem s001gmu@nova.wright.edu
    • • Marion's Tailor Problem Damion Schubert
    • Marion's Tailor Problem Damion Schubert
    • • Marion's Tailor Problem Ola Fosheim Grøstad
  • Marion's Tailor Problem Adam Wiggins
  • • Marion's Tailor Problem quzah
    • Marion's Tailor Problem Marian Griffith
    • Marion's Tailor Problem J C Lawrence
    • • Marion's Tailor Problem Marian Griffith
      • • Marion's Tailor Problem Koster, Raph
  • Marion's Tailor Problem Matthew R. Sheahan
  • • Marion's Tailor Problem quzah
    • • Marion's Tailor Problem Matthew R. Sheahan
  • Marion's Tailor Problem Koster, Raph
  • • Marion's Tailor Problem Marian Griffith
    • • Marion's Tailor Problem Ola Fosheim Grøstad
      • • Marion's Tailor Problem J C Lawrence
        • • Marion's Tailor Problem Ola Fosheim Grøstad
        • Marion's Tailor Problem Marian Griffith
• Slightly-OT: RPG Mapping Tool Holly Sommer
• UBE/high: UBE/high: FW: UBE/high: W IRED: Kilers Dr. Cat
• UBE/high: FW: UBE/high: W IRED: Kilers Scatter
• • UBE/high: FW: UBE/high: W IRED: Kilers Marian Griffith
  • • UBE/high: FW: UBE/high: W IRED: Kilers Scatter
    • UBE/high: FW: UBE/high: W IRED: Kilers Brandon J. Rickman
    • • UBE/high: FW: UBE/high: W IRED: Kilers Damion Schubert
      • • UBE/high: FW: UBE/high: W IRED: Kilers quzah
        • UBE/high: FW: UBE/high: W IRED: Kilers Marian Griffith
      • UBE/high: FW: UBE/high: W IRED: Kilers Adam Wiggins
      • UBE/high: FW: UBE/high: W IRED: Kilers Travis Casey
      • • UBE/high: FW: UBE/high: W IRED: Kilers Brandon J. Rickman
        • • UBE/high: FW: UBE/high: W IRED: Kilers Koster, Raph
• Thoughts on Marian's Tailor Problem s001gmu@nova.wright.edu
• Standard Mud Room Format? plateau
• • Standard Mud Room Format? T. Alexander Popiel
  • • Standard Mud Room Format? Michael.Willey@abnamro.com
  • Standard Mud Room Format? J C Lawrence
  • Standard Mud Room Format? Adam J. Thornton
  • Standard Mud Room Format? Holly Sommer
  • • Standard Mud Room Format? Matthew R. Sheahan
  • Standard Mud Room Format? Hans-Henrik Staerfeldt
  • Standard Mud Room Format? Scatter
• Tangent to the Tailor Marc Bowden
• PerLDAP, usefull for your perl-mud? quzah
• UBE/high: Affordances and social method Dr. Cat
• UBE/high: FW: UBE/high: W IRED: Kilers have more fun Dr. Cat
• Article: A Summary of Principles for User-Interface Design. J C Lawrence
• • Article: A Summary of Principles for User-Interface Design. Adam J. Thornton
  • Article: A Summary of Principles for User-Interface Design. Ola Fosheim Grøstad
• Sockets permanently in CLOSE_WAIT state. (fwd) Oliver Jowett
• Fw: BlackSquad Releases File Formats Damion Schubert
• Revenants (Marion's Tailor Problem) Damion Schubert
• Finer points of Telnet programming ... Jynx {Wyrm / Tygr / Myth} Ryn
• • Finer points of Telnet programming ... quzah
  • • Finer points of Telnet programming ... J C Lawrence
    • • Finer points of Telnet programming ... quzah
      • • Finer points of Telnet programming ... J C Lawrence
  • Finer points of Telnet programming ... Marc Hernandez
  • Finer points of Telnet programming ... Ben Greear
  • • Finer points of Telnet programming ... Greg Munt
    • • Finer points of Telnet programming ... Ben Greear
  • Finer points of Telnet programming ... Jynx {Wyrm / Tygr / Myth} Ryn
  • • Finer points of Telnet programming ... Caliban Tiresias Darklock
    • • Finer points of Telnet programming ... Adam Wiggins
      • • Finer points of Telnet programming ... Caliban Tiresias Darklock
    • Finer points of Telnet programming ... quzah
  • Finer points of Telnet programming ... Greg Munt
• [off-topic] Email Jeroen Ruigrok/Asmodai
• Minimal MUD-kernel (was Finer points of Telnet programming ...) Niklas Elmqvist
• Modular MUD [Was:Finer points of Telnet programming ...] Jynx {Wyrm / Tygr / Myth} Ryn
• • Modular MUD [Was:Finer points of Telnet programming ...] Caliban Tiresias Darklock
  • • Modular MUD [Was:Finer points of Telnet programming ...] Adam J. Thornton
    • • Modular MUD [Was:Finer points of Telnet programming ...] Caliban Tiresias Darklock
      • • Modular MUD [Was:Finer points of Telnet programming ...] Adam J. Thornton
        • • Modular MUD [Was:Finer points of Telnet programming ...] Caliban Tiresias Darklock
          • • Modular MUD [Was:Finer points of Telnet programming ...] pomales
            • • Modular MUD [Was:Finer points of Telnet programming ...] Caliban Tiresias Darklock
              • Modular MUD [Was:Finer points of Telnet programming ...] Caliban Tiresias Darklock
              • • Modular MUD [Was:Finer points of Telnet programming ...] pomales
          • Modular MUD [Was:Finer points of Telnet programming ...] Jeroen Ruigrok/Asmodai
          • • Modular MUD [Was:Finer points of Telnet programming ...] James Wilson
    • Modular MUD [Was:Finer points of Telnet programming ...] Jynx {Wyrm / Tygr / Myth} Ryn
    • • Modular MUD [Was:Finer points of Telnet programming ...] Caliban Tiresias Darklock
• Modular MUD Caliban Tiresias Darklock
• • Modular MUD Ola Fosheim Grøstad
  • • Modular MUD Caliban Tiresias Darklock
    • Modular MUD Jeroen Ruigrok/Asmodai
    • • Modular MUD D. B. Brown
      • • Modular MUD quzah
        • • Modular MUD Caliban Tiresias Darklock
          • • Modular MUD Adam J. Thornton
            • • Modular MUD Caliban Tiresias Darklock
              • • Modular MUD Adam J. Thornton
                • • Modular MUD quzah
                  • • Modular MUD J C Lawrence
                    • Modular MUD Adam J. Thornton
                    • • Modular MUD Bruce Mitchener, Jr.
                      • Modular MUD Holly Sommer
                      • • Modular MUD Adam J. Thornton
                    • Modular MUD Caliban Tiresias Darklock
                  • Modular MUD Vadim Tkachenko
                  • Modular MUD John Bertoglio
• Modular MUD [Was:Finer points of Telnet progra Jon A. Lambert
• OS Wars [Was: Modular MUD] Jynx {Wyrm / Tygr / Myth} Ryn
• Modular MUD [Was:Finer points of Telnet progra Jon A. Lambert
• Modular MUD [Was:Finer points of Telnet programming ...] Chris Gray
• The 'consider' command Richard Woolcock
• • The 'consider' command Damion Schubert
  • • The 'consider' command Jon Leonard
  • The 'consider' command Hans-Henrik Staerfeldt
• Scripting:was Modular Mud Jon A. Lambert
• Quake 3: How to do OpenGL J C Lawrence
• lockless system - foolproof? James Wilson
• • lockless system - foolproof? Chris Gray
  • • lockless system - foolproof? J C Lawrence
    • lockless system - foolproof? James Wilson
  • lockless system - foolproof? J C Lawrence
  • • lockless system - foolproof? James Wilson
    • • lockless system - foolproof? J C Lawrence
      • • lockless system - foolproof? T. Alexander Popiel
        • • lockless system - foolproof? J C Lawrence
          • • lockless system - foolproof? T. Alexander Popiel
            • • lockless system - foolproof? J C Lawrence
        • lockless system - foolproof? James Wilson
        • • lockless system - foolproof? J C Lawrence
• Admin: OS wars and avocacy are off-topic J C Lawrence