Path: utzoo!utgpu!watserv1!watmath!att!occrsh!uokmax!apple!usc!wuarchive!swbatl!jmd
From: jmd@swbatl.sbc.com (Jim Doherty 5-0804 11-Y-03)
Newsgroups: comp.lang.c++
Subject: Re: OO Development Environments
Summary: Problems with ObjectStore
Keywords: C++, Object Design Inc, ODI
Message-ID: <1990Sep6.003405.24689@swbatl.sbc.com>
Date: 6 Sep 90 00:34:05 GMT
References: <1716@dinl.mmc.UUCP> <181@srchtec.UUCP> <1719@dinl.mmc.UUCP> <1723@dinl.mmc.UUCP>
Organization: Southwestern Bell
Lines: 49

In article <1723@dinl.mmc.UUCP>, noren@dinl.uucp (Charles Noren) writes:
> In article <26DC7CC4.266D@tct.uucp> chip@tct.uucp (Chip Salzenberg) writes:
> 
> >ODI's compiler is NOT, repeat, NOT a C++ compiler.  It does not
> >compile the C++ language.  Rather, it compiles a proprietary superset
> >of C++.  ODI's library is written in that superset of C++.  Using ODI
> >as an example of a C++ vendor is incorrect at best.
> >
> 
> ...yes, the Object Design Inc (ODI) C++ compiler is a proprietary
> superset of C++.  I gave a poor example.  However, while the ODI C++
> compiler does not make sense for a general C++ application, it was
> designed for use with ObjectStore, the Object-Oriented Database
> Management System from ODI -- and it makes very good sense to use it in
> an OODBMS application.  

	I agree that this is a good implementation however if you are developing
	any type of time critical (real time, with usual disclaimers 
	about real time) you will find that ObjectStore blocks on I/O and therefore
	your concurency within a process is well single threaded at that point !

>ODI's C++ with ObjectStore provides a seamless
> interface between the C++ applicaton and the OODBMS.  Sure you will not
> be compatable with the rest of the world, but I don't see how that can
> be avoided with any other OODBMS I've looked at (admittedly a small
> subset, ObjectStore, OntoLogic, Gemstone), since you are locked into
> their proprietary interface and class library.  The best that could be
> done, I think, is to encapsulate the OODBMS interface into some classes
> that would be rewritten if a port to a different OODBMS is necessary.

	chuck makes a good point here in our case we have decided to roll
	our own interface to Sybase(which is what ObjectStore uses I believe) as
	a backend storage dbms. At some point you will have to hide your apps
	from the dbms or of course role your own.
> 
> 
> -- 
> Chuck Noren
> NET:     dinl!noren@ncar.ucar.edu
> US-MAIL: Martin Marietta I&CS, MS XL8058, P.O. Box 1260,
>          Denver, CO 80201-1260
> Phone:   (303) 971-7930


-- 
James M Doherty  - SWBT - Advanced Technology Planning
One Bell Center Room 11-Y-03 St. Louis, Mo. 63101
UUCP: { pyramid, ihnp4, bellcore }...!swbatl!jmd
PHON: 314-235-0804 FAX: 314-235-0727