|Revision as of 07:54, 5 September 2006
126.96.36.199 (Talk | contribs)
← Previous diff
|Revision as of 14:55, 5 September 2006
Wayne (Talk | contribs)
Reverted edit of 188.8.131.52, changed back to last version by 184.108.40.206
Next diff →
|Line 1:||Line 1:|
|-||'''CCBANGNING Community'''||+||==[http://www.sdsc.edu/srb/jargon 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.|
|+||===[[Scommand]]-like example utilities===|
|+||===[[ImageJ Plugins]]=== A set of 2 simple plugins designed to support an ImageJ connection to the Storage Resource Broker.|
|+||==How To: Using Jargon==|
|+||*[http://www.sdsc.edu/srb/jargon/Intro_Jargon.ppt Introductory Jargon API PowerPoint presentation]|
Revision as of 14:55, 5 September 2006
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.
Scommand-like example utilities
How To: Using Jargon
The SRB Clients are distributed by the University of California under the BSD License:
Copyright (c) 2006, Regents of the University of California All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the University of California, San Diego (UCSD) nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
To get extra debugging information launch your JVM with the jargon.debug variable set from 0-6, e.g.
Or add the following line of code before instantiating any Jargon java objects.
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.