[377] in Tooltime
Update on Scopus SQL*Net
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Mon Jan 27 08:27:35 1997
Date: Mon, 27 Jan 1997 08:31:02 +0100
To: tooltime@MIT.EDU
From: Steven Wade Neiterman <wade@MIT.EDU>
I have had conversations with Scopus each day last week on progress with
the Scopus SQL*Net client. I decided that Scopus needs to write up the
notes from the discussion so that we have their words in writing. I should
get this later today and will send it along.
Two weeks ago, we received an updated Scopus client built on the SQL*Net
2.0 library. Well, not only did this not work with OT 1.1.2, but I do not
believe that Oracle supports this version of SQL*Net. Turns out, Scopus
had the 2.0 library since the Summary of '95 and decided to use it instead
of getting a more recent version. Once I reported this to Scopus, they
then ordered a 2.1 library from Oracle.
The short summary is that once Scopus obtained the 2.1 version of SQL*Net
for the Macintosh, they realized that it was built using CFM (Apple's Code
Fragment Management - which replaced the older Apple Shared Library
Management). This became difficult for Scopus to handle.
So, the good news. Scopus will compile a Scopus 5.2 client instead of
3.6.2.1 client. The 5.2 client is a cross compiled version of the Windows
code and thus should have not only better memory management (e.g. using
CFM) and thus work faster, but it shares the same code base and should
resemble more of the Scopus Windows client.
So, the bad news. Building, testing and release of a 5.2 client will take
four weeks from last week.
The other information I am checking into is what is in a 5.2 release. This
is the release number that was slated for the Summer '97. My guess is that
they will recompile the 3.6.2.1 client base into 5.2 and not have the new
functions of the "real" 5.2. This still needs clarification.
As I get written timelines and clairification, I will send it along.
..Steve
