SREG 1.1 Request parameters

Enis Soztutar enis.soz.nutch at gmail.com
Thu Feb 21 13:35:05 UTC 2008


Hi,

As far as I understand, the distinction between sreg.required and 
sreg.optional is entirely in the responsibility of the consumer and 
there is not reason for the protocol to include this arbitrary division. 
An OP implementation will just merge the two fields and try to fill them 
as much as it can.

I propose we merge this two fields for version 1.1. This will introduce 
another backwards compatibility rule, but I think this design will be 
better.

Enis Söztutar



More information about the specs mailing list