[comp.os.mach] data base & tasks & threads

dennisg@kgw2.bwi.WEC.COM (Dennis Glatting) (02/16/91)

i'm looking for a data abse package that runs on the NeXT.  it must be 
a server and support multiple tasks and multiple threads within those tasks.

does anyone know of such a package and what are yor experiances?
will SYBASE suport multi threaded apps.

i'll give an example of my usage.
i have several tasks that accepts mail from different sources.  for example
one task could be collecting mail a network device.  another task could be 
accepting mail from devices connected via serial link.  now i have multiple
mail delivery tasks.  some deliveries go over the network, others go over
serial interfaces.  (this isn't mail in UNIX mail sense.)  so, as you see, 
there is a lot of data base interaction both amoung tasks and threads
within those tasks.

please respond via mail.  i don't get news.

-- 
 ..!uunet!kgw2!dennisg  | Dennis P. Glatting
 dennisg@Xetron.COM     | X2NeXT developer
                        | NeXT/C++/Objective-C wienie

dennisg@kgw2.bwi.WEC.COM (Dennis Glatting) (02/19/91)

sorry for the repost, postnews uses the wrong return address


In article <1897@kgw2.bwi.WEC.COM>, dennisg@kgw2.bwi.WEC.COM (Dennis Glatting) writes:
|> i'm looking for a data abse package that runs on the NeXT.  it must be 
|> a server and support multiple tasks and multiple threads within those tasks.
|> 
|> does anyone know of such a package and what are yor experiances?
|> will SYBASE suport multi threaded apps.
|> 
|> i'll give an example of my usage.
|> i have several tasks that accepts mail from different sources.  for example
|> one task could be collecting mail a network device.  another task could be 
|> accepting mail from devices connected via serial link.  now i have multiple
|> mail delivery tasks.  some deliveries go over the network, others go over
|> serial interfaces.  (this isn't mail in UNIX mail sense.)  so, as you see, 
|> there is a lot of data base interaction both amoung tasks and threads
|> within those tasks.
|> 
|> please respond via mail.  i don't get news.
|> 

-- 
 ..!uunet!kgw2!dennisg  | Dennis P. Glatting
 dennisg@Xetron.COM     | X2NeXT developer
                        | NeXT/C++/Objective-C wienie

dlw@odi.com (Dan Weinreb) (02/20/91)

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.