| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1409.1 | I think not new | OSAV03::NOSE | Tooru Nosse, Japan West PSC/OS2 | Fri May 23 1997 11:36 | 28 |
| Hi John.
>The length of objrefs now seems to depend on the number of
>attributes and operations in the interface. Is this true?
>(It didn't use to be, right?).
Objref contains all of the information to bind METHOD since ** V2.5B **
(Below are that of V2.5B)
Interface UUID
For each operation:
operation uuid
operation index
For each bound implementation:
Implementation ID
binding policy
activation type
operation mask (bitmap to show implemented operation)
Server instance ID
Server location
etc.
(In the day of V2.5B, I did analyze and PATCH OBJREF that was broken
because of OBB's bug :-).
Yes, Large Interface had surely very large objref.
I don't know V2.7 well, so I can't write about it.
/Toru
|
| 1409.2 | | LEMAN::DONALDSON | Froggisattva! Froggisattva! | Fri May 23 1997 12:26 | 17 |
| Tooru. Many thanks.
I guess I just hadn't noticed in 2.5 and 2.6.
Just to tell the story. I've been adding to a
test set (to test different sequences) and adding
ooprations to one interface. At a moment I started
getting a corrupted objref. It turned out that
my char array was only 1500 bytes! And I'd gone
past that.
I surely would like the contents of an objref properly
documented, and an objref dissasembler. (I've got
something but it doesn't pull out everything in your
list, just interface, impl, ref data and bindings).
John D.
|
| 1409.3 | I sent my analysis to John | OSAV03::NOSE | Tooru Nosse, Japan West PSC/OS2 | Sat May 24 1997 00:37 | 1 |
|
|
| 1409.4 | | REQUE::BOWER | Peter Bower, ObjectBroker | Sun May 25 1997 10:27 | 3 |
| With IIOP, stringified object references will not have attribute
and operation information.
|