From beringer@DB.Stanford.EDU Wed May 27 16:03:54 1998 Received: from Sealion.Stanford.EDU (Sealion.Stanford.EDU [171.64.75.55]) by DB.Stanford.EDU (8.8.8/8.8.8) with SMTP id QAA01072 for ; Wed, 27 May 1998 16:03:26 -0700 Sender: beringer@DB.Stanford.EDU Message-ID: <356C9C63.510@db.stanford.edu> Date: Wed, 27 May 1998 16:06:11 -0700 From: Dorothea Beringer X-Mailer: Mozilla 3.01Gold (X11; I; HP-UX A.09.05 9000/712) MIME-Version: 1.0 To: chaims@DB.Stanford.EDU Subject: Minutes weekly meeting 5/28/98 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mozilla-Status: 0001 Content-Length: 2504 Minutes weekly meeting 5/28/98 ============================== Status reports: RMI-wrappers: Catherine is putting ASN.1 into wrappers, changing from strings to ASN.1 has resulted in many changes. CORBA-wrappers: Hao has added GetParam into wrappers, yet so far some weird errors appear. Baby-demo: Problem: C++-client produced by Woody refuses to talk to java-io-megamodule (ORB dumps). Kazuki will try to make a C++ client for IO-megamodule.... Scheduler: inserting of terminate nearly completed. Compiler for RMI-client: As it turns out, the transportation modules translated into Java by Mehul are not CHAIMS-compliant and therefore Mehul cannot use them for testing his generated RMI-client. Various open points: Open point 1: what happens when network connection is lost? (timeout, ping for testing if machine is still there, ark for checking if a specific port is still occupied,....) Open point 2: terminating megamodules: megamodule cannot determine which active invocations it has to close down, because it does not know which ones are from which client ==> before the megamodule connection is closed down, the client has to terminate each invocation ==> compiler has to create code for making list of active invocations Talk Hao about wrappers: Wrapping megamodules: make copy of TestModule.cc and make changes to SetFunc, InvokeMethod and getparam. Open point 3: setattr (setting global attributes), how to implement? Problem: global attributes should not be shared by several clients ==> they only should be changed for all following invocations of a specific client ==> megamodule would need notion of who is making a specific invokation and managing which invocations and "global" parameters belong to which client.... this problem is related to open point 2 above. RMI: object openconnection could contain the information about which socket has connected to a server and from whom a method call comes; is this knowledge accessable? CORBA: this knowledge is hidden from the user TCP/IP: every package includes the knowledge about from whom it comes ==> question once again is: what really want we use setattribute for? what kind of megamodules will support that? support it how? examples? Finally Hao presented what to do to wrap a megamodules (make copy of TestModule.cc and make changes to SetFunc, InvokeMethod and getparam). -- Dorothea Beringer Stanford University beringer@db.stanford.edu http://www-db.stanford.edu/people/beringer.html --