From: JustinBl@osiristrading.com   
      
   I know its off topic but have you also considered the security   
   implications? Javascript is visible in the browser, the user can run   
   unsensored SQL against your data and inject sql into your pages   
   running existing sql to do stuff you hadn't considered. But it sounds   
   cool anyway. Would you give an example of how you intend to use your   
   idea and a walk through of how it would work ? I am confused between   
   whether the data sits in JS in the HTML page and then your DBMS in JS   
   allows users to browse to you page and run queries against the data   
   using SQL all in JS, or the data sits somewhere else and you actually   
   connect to your page and then connect through your JS DBMS to the data   
   elsewhere and run it like that or is the data input onto the page and   
   works off memory?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)