| Martin,
Since v3.0 hasn't shipped yet then I doubt whether anyone has even
thought about this let alone tried this... and as Tony says without
access to the sources and a BLISS compiler it's impossible let alone
the fact that you'd never be able to get hold of them.
Oh and it wouldn't be just the OADDS object you'd need some of teh MAIL
modules also and since those have lots of changes in them for Shared
Filing and SMU and .. so you'd need the CABINET modules and since those
have changes in them for the FCS you'd need that and before long you'd
have the whole v3.0 kit.
Wait for v3.0 and then upgrade as they say patience is a virtue
But of course I know nothing about DDS (:==:)
Regards,
Andrew.D.Wicks
|
|
Hi Andrew & Tony,
"Just wait for V3.0"...
The customer that wants better DDS behaviour implemented, just
upgraded to ALL-IN-1 V2.4 Dutch (Nederlands).
We expect ALL-IN-1 IOS V3.0 Nederlands not to be available before
the end of this calender year, probably later...
As you state, lots of changes appeared in the new V3.0 forms,
named data & bliss code of the Electronic Mail Subsystem.
The reason for my question is the fact we implemented DDS for the
whole customer ALL-IN-1 population.
We want to implement consistant use of DDS from ALL-IN-1 IOS,
without the inconsistant behavior like : first search remote
addressee on World Search node; next time find this addressee in
cache, using different ALL-IN-1 options...
The V3.0 DDS behavior of ALL-IN-1 is much more consistant in this
area...
But, as I see and referring to your answers, I'll wait for
ALL-IN-1 V3.0.
By the way, we disabled all DDS caches on DDS Local Nodes to force
consistent DDS behavior...our World search nodes can handle it !
FYI :
Lots of departemental ALL-IN-1 systems are being installed at the
moment. The total population will grow to �5000 ALL-IN-1 IOS Users
in the coming 1� year.
Currently the ALL-IN-1 population consists of �1300 users. Also
ICL adressees and external mail users are registered in the DDS
database.
Regards,
Martin
|