From - Fri Mar 26 12:41:57 1999 Received: from db.stanford.edu (Seaotter.Stanford.EDU [171.64.75.89]) by DB.Stanford.EDU (8.8.8/8.8.8) with ESMTP id MAA04073 for ; Fri, 26 Mar 1999 12:35:09 -0800 Message-ID: <36FBF082.13C7188E@db.stanford.edu> Date: Fri, 26 Mar 1999 12:39:30 -0800 From: Dorothea Beringer Organization: Stanford University X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: chaims@DB.Stanford.EDU Subject: Minutes last meeting Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mozilla-Status: 8001 Date[ March 23, 1999 ] Recordnr[ ] Who[ gw, db, lm, ns Agenda[ - Trip report Gio - Work items for Neal and Laurence for spring - Meeting time next term Minutes[ Meeting time next term: Tuesday, 2pm: temptative meeting time Gio trip report: presented CHAIMS at ETHZ. Scheck: overlaps transactions over large processes. How do we handle interactions? - locking of resources used by several megamodules: the megamodules have to interact among themselves to solve these problems, hidden from client/megaprogram - overall transactions (travel arrangements): explicit methods for transaction handling (e.g. Cancelflight for flight reservation server) Possible tasks for next term 1) Preprocessing scheduling for exploiting parallelism: preparatory work 2) Run-time scheduling for exploiting parallelism based on graph, preparatory investitations - develop concepts - complexity? - what can be done with it? 3) Cost-function for service selection and preemptive method execution (in case of functional depenendcy without data dependancy) - study query optimization, AND-OR DAGs, (is there a class about that?) 4) Literature search, scheduling 5) Do some implementation work 4) Incremental extraction - white paper 5) Dataflow - controlflow - white paper 6a)Graphical front-end: study other approaches (PIF, ....) 6b)Graphical front-end: define something.... and implement it and make at least one representable demo/example with it. 7) something else? CHAIMS and e-commerce: see also Steve Katchel My idea: subscription for just one or several services: sign-up via web-page like for other services (telecommuication) or products (books). Then client gets username and password that are used in SETUP command in the megaprogram. The provider then charges the client periodically or each time via credit card or for whatever scheme the client has signed up. -- Dorothea Beringer Stanford University beringer@db.stanford.edu http://www-db.stanford.edu/people/beringer.html --