Re: Large MOOs

• Date: Mon, 18 Nov 1996 17:13:03 PST
• From:
  "John Towell Ph.D." <m50jft1@hayek.cob.niu.edu>
• Cc: m50jft1@hayek.cob.niu.edu
• In-Reply-To: <3.0.32.19961118162058.009015b0@intmail.romt.com>; from "Will Orton" at Nov 18, 96 4:20 pm
• Mailer: Elm [revision: 70.85.2.1]

> 
>    My company is looking into the possibility of using a MOO for a large,
> internal WWW database/server. We anticipate the addition of about 10,000
> object a month (bug reports, customer calls, etc). I know of MOOs that have
> object counts into the 10s of thousands, but how about 200,000 to 400,000
> or more?

But why would you store these objects containing information in the MOO itself?
Just keep the information in external files and use FUP.
Or better yet, keep the information in a regular database and query the 
database from inside the MOO. At NIU I have a MOO running that has an 
object (called the Query Machine) that will take an SQL query, send it
to a Sybase Database running on the same machine and bring the result of
the query back into the MOO.  No need to bloat the MOO database with
information that could be kept outside.  
>  
> Thanks for any info or pointers...


This should bring some interesting responses. :)

Cheers!

John (aka Watson Crick - BioMOO Wiz) 
--
                                  -----------------------------------------
John Towell, Ph.D.               |   "Among the many virtues of text-based | 
Post-doc: Informatics            |      Networked Virtual Environments     |
Northern Illinois University     |       is lack of having to take notes." |
                                 |               ... Watson Crick          |
m50jft1@131.156.1.191             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
http://131.156.1.191/server/m10ert1/ECCC/johnhome.html

• Large MOOs
• From: Will Orton <worton@romt.com>

• Prev: Re: Large MOOs
• Next: Re: Large MOOs
• Index: MOO-cows
• Thread: MOO-cows