From: Taral <taral@cyberjunkie.com>
To: pgsql-interfaces@hub.org
Subject: CORBA object lifetime problems
Date: Sun, 15 Nov 1998 10:30:24 -0600
Message-ID: <000001be10b5$3ed4a1c0$8a14f7d0@taral.dobiecenter.com> (raw)
There's a problem with implementing CORBA... it was brought up in some docs
I read, but I didn't realize until now that it was important.
Servant objects will be created on the server side in response to queries
from the clients. When should these objects be disposed of? A dispose()
method is good, but what if the client just disappears? We cannot rely on
the proper behavior of the client. (Who knows with the Internet as
unreliable as it is? :)
The best I've thought of so far is to have a thread in the server clean up
old queries that are left behind by accident (shouldn't be too often), and
provide keepalive() and dispose() methods... But how long an interval should
we use?
Also, do we provide query regeneration? Maybe a rerun() on the query result
object? Of course, that requires that we keep the query on the server
side...
Or am I the only one left working on this because the 900+ page CORBA spec
scared everyone else off? *grin*
Taral
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-interfaces@postgresql.org
Cc: taral@cyberjunkie.com, pgsql-interfaces@hub.org
Subject: Re: CORBA object lifetime problems
In-Reply-To: <000001be10b5$3ed4a1c0$8a14f7d0@taral.dobiecenter.com>
References: <000001be10b5$3ed4a1c0$8a14f7d0@taral.dobiecenter.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox