WP3 Relational Work Progress Report 11/5/2001 Steve Fisher / RAL

11 May 2001WP3 relational work - Steve Fisher/RAL2 Why relational Consider an alternative to the LDAP based MDS approach Relational model is much more powerful but LDAP is easily distributed May finally mix and match Plan to know where we are going by M9

11 May 2001WP3 relational work - Steve Fisher/RAL3 What is it Follow GMA from GGF Servlets for producers and probably also consumers (so that we can stream data to a consumer) Servlet which accesses MySQL via JDBC receiving a query and send back reply wrapped in XML – all using standards: –http(s) –XML –SQL

11 May 2001WP3 relational work - Steve Fisher/RAL4 Current technologies Using many existing technologies –Tomcat (servlet engine) –Javacc to build SQL parser Started from some donated code –JUnit – for testing “extreme programming” –Ant – for handling the builds –Dom parser to parse XML –and of course Java we are avoiding anything which will make it hard to write a C++ client Keep the client small

11 May 2001WP3 relational work - Steve Fisher/RAL5 Where are we Existing technologies understood Servlet which will accept SQL and return XML wrapped tables Ability to parse the returned XML Ability to parse almost complete SQL syntax and build a parse tree –Needed for query splitting Registration schema defined Tool to query registry Web page giving access to all the code etc. –

11 May 2001WP3 relational work - Steve Fisher/RAL6 Immediate Plans Submitting poster with supporting paper to BNCOD Manfred and Abdes to receive Java training API gets highest priority –but we need a basic system behind the API to make sure we have got it right. –Fix the registration (of pre-existing tables) - Manfred and James –Progress the API consumer/producer interactions - Abdes and Steve