Received: from id.godlike.com (id.godlike.com [206.205.199.129]) by hub.org (8.9.1/8.9.1) with ESMTP id LAA16694 for ; Sun, 15 Nov 1998 11:30:25 -0500 (EST) (envelope-from taral@cyberjunkie.com) Received: from taral ([208.247.20.138]) by id.godlike.com (8.8.5/8.8.5) with SMTP id LAA22905 for ; Sun, 15 Nov 1998 11:30:24 -0500 (EST) From: "Taral" To: Subject: CORBA object lifetime problems Date: Sun, 15 Nov 1998 10:30:24 -0600 Message-ID: <000001be10b5$3ed4a1c0$8a14f7d0@taral.dobiecenter.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal 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