PROTOCOL DESCRIPTION FOR THE SLICED PROTOCOL
============================================

By jchillerup.


Formal description
------------------
 


Test conversations
------------------

The first example of a test conversation correctly gets a chunk of numbers from a larger list. By using the REQUEST keyword, the server creates an ident tag for the particular user that is used when the user submits back data for sliced. It moves a file from /todo to /pending, renaming it at the same time in order to include this ident in the filename.

< This is sliced. Where do you want to go today?
> REQUEST
< IDENT: xyz.foo
< 37493
< 54640
< 90565
 (...)
< END
> OK
> BYE


The next example is almost the same, but the client does not send the required OK, making sliced put back the file into the todo pool.

< This is sliced. Where do you want to go today?
> REQUEST
< IDENT: xyz.foo
< 37493
< 54640
< 90565
 (...)
< END



This example demonstrates submission. The URLs are submitted in the same order as the URL seeds were given. If the URL seed does not resolve to anything, an empty line is entered.

< This is sliced. Where do you want to go today?
> SUBMIT
> xyz.foo
> http://url1.com
>    (... nothing ...)
> http://url3.com
(...)
> END
< OK
> BYE

After this example there will be a file in /done with the first three lines:

37493 = http://url1.com
54640 = 
90565 = http://url3.com



This last example touchs the IGIVEUP keyword. It is used when the user for some reason cannot complete his/her chunk.

< This is sliced. Where do you want to go today?
> IGIVEUP
> xyz.foo
< OK
> BYE