TSSP Procedures: Difference between revisions

From ReddNet
Jump to navigation Jump to search
mNo edit summary
Line 69: Line 69:
  <td align=center>F</td>
  <td align=center>F</td>
  <td>
  <td>
# empty depot set
# malformed query
# invalid schema
# invalid schema
# null result
  </td>
  </td>
  <td>
  <td>
# -
# -
# -
# -
# -
Line 113: Line 115:
  <td align=center>1</td>
  <td align=center>1</td>
  <td align=center>F</td>
  <td align=center>F</td>
  <td>-</td>
  <td>
  <td>-</td>
# malformed query
# invalid schema
</td>
  <td>
# -
# -
</td>
</tr>
</tr>
<tr>
<tr>

Revision as of 10:30, 3 January 2008

This section contains recommendations pertaining to the Issues section of the TSSP Framework article.

(back to Protocol Standardization Efforts)

Fault Tolerance

StepOccurrenceParallel (T/F)Failure TypeProcedure
obtain metadata 5 F
  1. connection timed out
  2. authentication failed
  3. path not found
  4. permission denied
  5. connection broken
  6. transfer canceled
  7. client destroyed
  8. size mismatch
  9. invalid schema
  1. -
  2. -
  3. -
  4. -
  5. -
  6. -
  7. -
  8. -
  9. -
fill channel 3 T - -
obtain depot set 2 T
  1. connection timed out
  2. authentication failed
  3. empty set returned
  4. connection broken
  5. lookup canceled
  6. invalid schema
  1. -
  2. -
  3. -
  4. -
  5. -
  6. -
determine next depot 2 F
  1. malformed query
  2. invalid schema
  3. null result
  1. -
  2. -
  3. -
reserve channel 2 T - -
publish/record metadata 2 F
  1. connection timed out
  2. authentication failed
  3. path not found
  4. permission denied
  5. not enough space
  6. connection broken
  7. transfer canceled
  8. client destroyed
  1. -
  2. -
  3. -
  4. -
  5. -
  6. -
  7. -
  8. -
order depot set 1 F
  1. malformed query
  2. invalid schema
  1. -
  2. -
expire channel 1 T - -
consume content 1 T - -
channel duration 1 T - -
channel capacity 1 T - -