Changes between Version 5 and Version 6 of MsXBrain

Timestamp:

09/19/06 11:27:52 (13 years ago)

Author:

ebmoore

Comment:

--

MsXBrain

@@ -29 +29 @@
  1. Because of #1, I have to encode the results or the query into a URL (I opted for the query using Base64 and GZip).
 
-To accommodate this, it takes the query as the post and then uses a distributed XQuery to get the results and process them when they are requested by MindSeer.
+To accommodate this, it takes the query as the post and then uses DXQP to get the results and process them when they are requested by MindSeer.
 
 == How it fits in ==
@@ -35 +35 @@
 http://sig.biostr.washington.edu/~ebmoore/MindSeerXBIntegration2.png
 
-While this diagram captures the XBrain System fairly accurately (with some simplification and completely leaving off the 2D image view), it fails to show how things are connected.  Conceptually, you can imagine distributed XQuery (dxquery) binding the system together.  Currently, there is no centralized server or library that does dxquery, but instead each component can use its own dxquery engine (unfortunately each engine has its own syntax).  In this case, MindSeer is integrated using AngloSaxon and the other components are integrated using a degenerate form of dxquery (just shipping the query and getting a document).
-
+While this diagram captures the XBrain System fairly accurately (with some simplification and completely leaving off the 2D image view), it fails to show how things are connected.  Conceptually, you can imagine distributed XQuery (dxquery) binding the system together.  DXQuery is not being done by DXQP using AngloSaxon.  As you can see in the image below, DXQuery (via DXQP) is what binds the whole system together on the backend and the XBrain portal is just the opening page.
 http://sig.biostr.washington.edu/~ebmoore/MindSeerXBIntegration.png
 
@@ -44 +43 @@
 
 http://sig.biostr.washington.edu/~ebmoore/User_Clicks_3D_Button.png
+''This image is slightly out of date''
  1. The XBrain User clicks on the 3D button and posts the XQuery to MsXBrain.
- 1. The XQuery is encoded and placed in the MindSeer launching file (JNLP file) as a URL
+ 1. An intermediate page allows the user to select a patient.
+ 1. The patient id, whether to use client/server and XQuery is encoded and placed in the MindSeer launching file (JNLP file) as a URL
  1. The JNLP file is returned to the XBrain User.
 
 http://sig.biostr.washington.edu/~ebmoore/Request_Map_File.png
+''This image is slightly out of date''
  1. MindSeer uses the URL to request a map file (Results.bmx?...)
  1. Tomcat sends the file to the MindSeer File servlet.
  1. MindSeer File requests the data using the encoded query.
- 1. AngloSaxon executes the query on the XCSM and TransformationServer
- 1. The resuls are returned to MindSeer to display to the user.
+ 1. AngloSaxon and DXQP execute the query on the XCSM and TransformationServer
+ 1. The results are returned to MindSeer to display to the user.
 
 == Distributed XQuery ==