Re: quick question on threads & remote stubs

• To: <ozone-users@ozone-db.org>
• Subject: Re: quick question on threads & remote stubs
• From: "Reason" <reason@exratio.com>
• Date: Sun, 1 Apr 2001 16:23:23 -0700
• Delivered-To: softw7-ozone-db:org-ozone-users@ozone-db.org
• Reply-To: "Reason" <reason@exratio.com>

>On Sun, 01 Apr 2001, Reason wrote:
>> If two separate threads within the same JVM call
>> ExternalDatabase.objectForName(name), do they receive references to the
same
>> stub object or to two different stub objects? In other words, does each
>> different thread within a single JVM requesting an interface to the same
>> persistant object require the creation of a new stub?
>
>Yes, each subsequent call of objectForName, regardless if this is in the
same
>or a different thread, creates and returns a new proxy object. proxy
objects
>are very small (6 bytes) so this should not be a problem. An object cache
could
>help to reduce the number of proxy objects in the VM but this would also
add an
>extra overhead to search in the cache each time a proxy is created.

Ok...how about references? e.g. you make an objectForName call for
persistant object X that contains references to persistant objects Y and Z.
You then get object Y via the reference and start working with it. In this
case, do you get a new proxy object with every call in the same thread to
the X.method() that returns Y?

Reason
http://www.exratio.com/

• Follow-Ups:
  • Re: quick question on threads & remote stubs
    • From: Falko Braeutigam <falko@smb-tec.com>

• Prev by Date: Re: revisiting the vanishing user (in Windows)
• Next by Date: build
• Prev by thread: Re: quick question on threads & remote stubs
• Next by thread: Re: quick question on threads & remote stubs
• Index(es):
  • Date
  • Thread