HP3000-L Archives

December 1997, Week 2

HP3000-L@RAVEN.UTC.EDU
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
New Image/sql package (was b-trees)
From:
Richard Gambrell <[log in to unmask]>
Reply To:
[log in to unmask][log in to unmask], 11 Dec 1997 13:29:06 -0500567_us-ascii If you are using disc limits, please reply to me privately with why you
do, what to take into account in so doing, and if you think that this
issue would be of general enough interest for me to post a digest of
what I get. Someone has consumed all available disc space on their
volume set twice now (other issues prevent isolating them to their own
volume set), and we have to consider applying disc limits if they cannot
behave. We also have to consider if we need to prohibit the NEWGROUP and
possibly the mkdir commands, so that [...]41_11Dec199713:29:[log in to unmask]
Date:
Wed, 10 Dec 1997 13:44:19 -0600
Content-Type:
text/plain
Parts/Attachments:
New (24 lines) 
>
> > 3. A "simple and standard" CORBA interface implementation (I think I got
> > that right) for the native Image calls and for the allbase SQL calls.
>
> I'm sorry, but you can't use "simple" and "CORBA" in the same sentence :-)
I was afraid of that - one of the reasons for the "quotes".:-)

>
> We're very close to being able to use Java RMI to access remote Image
> database objects on the 3000 from all kinds of Java client/server
> applications.  There are also a number of Pure Java CORBA compatible
> ORBs available or in development which may be one way to get CORBA
> onto MPE, though the Java RMI stuff is a lot easier and definitely
> more fun to work with.

RMI would be excellent and in keeping with the spirt of Image calls - i.e.
direct access to maximize performance without giving up reliability.

>
> G.
>

Richard Gambrell

ATOM RSS1 RSS2