Jakub Skoczen wrote:
>
>> I wonder if someone, like Kuba, could design an 'extended async SRU' on top
>> of SRU, that is very SRU like, but builds on top of it to add just enough
>> operations for Kuba's use case area.  I think that's the right way to
>> approach it.
>>     
>
> Is there a particular "extensibility" feature in the protocol that
> allows for this?
>   
I don't know, but that's not what I was suggesting. I was suggesting you 
read the SRU spec, and then design your own "SRU-async" spec, which is 
defined as "exactly like SRU 2.0, except it also has the following 
operations, and is identified in an Explain document like X."

Jonathan