Jargon

From SRB

(Difference between revisions)
Revision as of 00:55, 31 March 2006
Lucas (Talk | contribs)
Debugging Jargon
← Previous diff
Revision as of 21:15, 31 March 2006
Lucas (Talk | contribs)

Next diff →
Line 4: Line 4:
The data grid is a new and exciting development in computing, utilizing transparent replication, archiving, caching heterogenous storage, aggregated data movement, shadow objects and a lot of other things most people don't know, or want to know, much about. That's why JARGON has been designed from the ground up to make programming for the grid as straightforward as possible. The data grid is a new and exciting development in computing, utilizing transparent replication, archiving, caching heterogenous storage, aggregated data movement, shadow objects and a lot of other things most people don't know, or want to know, much about. That's why JARGON has been designed from the ground up to make programming for the grid as straightforward as possible.
-==Debugging Jargon==+==[http://www.sdsc.edu/srb/jargon Downloads]==
-To get extra debugging information launch your JVM with the jargon.debug variable set from 0-6, e.g.+===Example programs===
 +*[http://www.sdsc.edu/srb/jargon/Test.java Test.java]
 +*[http://www.sdsc.edu/srb/jargon/FactoryTest.java FactoryTest.java]
 +*[http://www.sdsc.edu/srb/jargon/MetaDataTest.java MetaDataTest.java]
- java -Djargon.debug=1+===[[Scommand]]-like example utilities===
 +*[http://www.sdsc.edu/srb/jargon/Sls.java Sls.java]
 +*[http://www.sdsc.edu/srb/jargon/Sput.java Sput.java]
 +*[http://www.sdsc.edu/srb/jargon/Sget.java Sget.java]
 +*[http://www.sdsc.edu/srb/jargon/Srm.java Srm.java]
-The extent of debugging information increases with higher values.+===[http://www.sdsc.edu/srb/matrix/cvs.cgi/jargon/ CVS]===
-0: No debuging information.  
-1: A number of methods in GeneralFile can actually result in IOExceptions due to failures communicating to the server. These exceptions are caught and handled within that GeneralFile method. However sometimes it can be useful to see what exceptions did occur. The stack trace of those exceptions are printed to System.err. As well as the name of each low level method call to the server. +==How To: Using Jargon==
 +{{:Jargon Tutorial}}
-2: Adds information about connection and authentication. Helps to insure you are connecting to the expected server as the correct user.  
-*Higher debugging levels get especially technical... 
-3: Adds information about the query return value.  
-4: Adds even more information about the query result and the actual query that was sent to the server. +==Debugging Help==
-*Debugging levels beyond here are probably only useful to a developer expanding the Jargon API.+{{:Debugging Jargon}}
-5: Adds the actual bytes sent to the sever by a query and the bytes returned from the server after a query.  
-6: Adds every byte sent on the socket connection to the server and every byte returned by the server. You'll probably want to read the section on the [[SRB protocol]]. 
==See Also:== ==See Also:==
*[http://www.sdsc.edu/srb/jargon/Intro_Jargon.ppt Introductory Jargon API PowerPoint presentation] *[http://www.sdsc.edu/srb/jargon/Intro_Jargon.ppt Introductory Jargon API PowerPoint presentation]

Revision as of 21:15, 31 March 2006

Contents

Jargon, A Java client API for the DataGrid

 	A new grid API, that you already know.

The data grid is a new and exciting development in computing, utilizing transparent replication, archiving, caching heterogenous storage, aggregated data movement, shadow objects and a lot of other things most people don't know, or want to know, much about. That's why JARGON has been designed from the ground up to make programming for the grid as straightforward as possible.

Downloads

Example programs

Scommand-like example utilities

CVS


How To: Using Jargon

Jargon Tutorial


Debugging Help

To get extra debugging information launch your JVM with the jargon.debug variable set from 0-6, e.g.

  java -Djargon.debug=1

Or add the following line of code before instantiating any Jargon java objects.

  System.setProperty("jargon.debug", "1");

The extent of debugging information increases with higher values.

0: No debuging information.

1: A number of methods in GeneralFile can actually result in IOExceptions due to failures communicating to the server. These exceptions are caught and handled within that GeneralFile method. However sometimes it can be useful to see what exceptions did occur. The stack trace of those exceptions are printed to System.err. As well as the name of each low level method call to the server.

2: Adds information about connection and authentication. Helps to insure you are connecting to the expected server as the correct user.

  • Higher debugging levels get especially technical...

3: Adds information about the query return value.

4: Adds even more information about the query result and the actual query that was sent to the server.

  • Debugging levels beyond here are probably only useful to a developer expanding the Jargon API.

5: Adds the actual bytes sent to the sever by a query and the bytes returned from the server after a query.

6: Adds every byte sent on the socket connection to the server and every byte returned by the server. You'll probably want to read the section on the SRB protocol.


See Also: