| Title: | ObjectBroker Desktop Connection |
| Moderator: | RECV::STORM |
| Created: | Mon Jan 06 1997 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 40 |
| Total number of notes: | 125 |
DTC User Guide Appendix B Type Mappings
float is not a valid VB Data Type,
do I use single or double instead ?
And doing a
Set SA = GetObject("4Digital.Obb.Bridge\ADAPTER\OBjectBroker\Advertisements\SaveAccount")
requires about 20 seconds on my Windows 95 System (66 Meg Pentium with
96Meg of Mem)
What is about to be expected to resolve Object's using the name server
(Advertisement Partition),
Also I can see that after starting up VB this long elapsed time happens
only once. each consecutive restart of the program takes just
miliseconds.
Otherwhise after crashing BANK11S, and restarting BANK11S
GetObject did not except (still beleaving that the SA Variable is
pointing to a valid ObjectReference, but
Call SA.Deposit(2001.55, newBalance)
raises an exception
Can someone explain the mystery about how long a VB Developer can treat
an ObjectReference (the one I receive after a GetObject) as
a) valid .... as long as ...
b) cached ... until ... event happens .... or ... or ...
c) invalidated by .....
d) a server crash .... has the following effect on .....
e) a agent crash .... has the following effect on .....
Sepp,
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 20.1 | SET TT:/COFFEEBREAK (when loading dlls) | PAMSRC::PROCTOR | say it with objects | Fri Feb 14 1997 13:05 | 11 |
Sorry about the long delay. Alot of the DTC loads an extensive
set of DLL's upon activation. The installation and initialization
of these dll's has gotten all our attention (believe me I develop
on a 486). If someone knows a way to install these dll's - please reply.
As for trusting your object reference, I tend to use my automation
interface inside a try/catch and deal with the exception to
invalidate my reference. I'm not a vb programmer though and don't
know how you can handle the exceptio there.
bob
| |||||
| 20.2 | Single | iceaxe.zko.dec.com::Rosen | Michael Rosen | Fri Feb 14 1997 17:41 | 12 |
> float is not a valid VB Data Type,
> do I use single or double instead ?
single
> Can someone explain the mystery about how long a VB Developer can treat
> an ObjectReference (the one I receive after a GetObject) as
I'll have to look into exactly where the caching is taking place. I'm not
sure offhand.
| |||||
| 20.3 | NUTS2U::LITTLE | ATG/EOS/Object Infrastructure/me | Thu Mar 06 1997 07:03 | 19 | |
I'm not sure what behavior you are reporting with regard to treating an
object reference. The reference you hold in VB to an object is an
interface pointer (as with any COM object). For a CORBA object, the
interface pointer VB is holding points to an in process proxy for the
CORBA object. Included in that proxy is the CORBA oref which is what
is used for invoking methods. As long as the oref can still be used by
ObjectBroker, the Visual Basic object reference should still be OK.
Without more information, it will be difficult to try and guess what
the exception was, although from what you reported, you should not have
recevied the exception.
Also, the startup times we know are long. We are currently bringing in
too much stuff from the repository, from the advertisement partition,
and others at startup time. The second and subsequent times in VB are
fast because VB doesn't unload the DLL and the startup is avoided.
-tl
| |||||