Xref: utzoo comp.os.mach:761 comp.sys.next:13019 comp.databases:8917
Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!odi!dlw
From: dlw@odi.com (Dan Weinreb)
Newsgroups: comp.os.mach,comp.sys.next,comp.databases
Subject: Re: data base & tasks & threads (repost)
Message-ID: <1991Feb19.203026.6404@odi.com>
Date: 19 Feb 91 20:30:26 GMT
References: <1897@kgw2.bwi.WEC.COM> <1899@kgw2.bwi.WEC.COM>
Reply-To: dlw@odi.com
Organization: Object Design, Inc.
Lines: 10
In-Reply-To: dennisg@kgw2.bwi.WEC.COM's message of 18 Feb 91 19:31:43 GMT

If you end up with a DBMS that does not, in itself, run in multiple
threads, you're not stuck.  You can just write your application so
that there is one particular thread that does all the DBMS
interactions.  The other threads would communicate with it, via
whatever inter-thread communication your operating system provides.
So one thread might be gather some mail from a serial line while
a second thread is dealing with the database.  When the first one
is done, it queues up a request to the second one, which will
immediately or eventually pick up the request and deal with the
database system.