Well, I agree this can be a good practice, but maybe that shouldn't belong to the spec then :(
On Sun, Jan 24, 2010 at 8:54 PM, Waleed Abdulla <[email protected]> wrote: > I'd guess it's to avoid overwriting existing params that my have the same > name as params used in the subscription verification process. By ensuring > that the verification params are at the end, a subscriber knows that their > own custom params are the ones that come first. It's probably and edge case, > but a good practice. > > from the specs, section 6.1.1 > >> Existing parameters with names that overlap with those used by >> verification requests will not be overwritten; Hubs MUST only append >> verification parameters to the existing list, if any. > > > > Waleed > > > > On Sun, Jan 24, 2010 at 3:44 AM, Julien Genestoux < > [email protected]> wrote: > >> While trying to make our hubs "compliant", I found that in section 6.1.1 >> that the query string parameters must be *at the end.* In Superfeedr's >> case, given how we build that for now, the position cannot be predicted. Is >> there a reason for that or can we accept that the quetry string param just >> have to be presevered, no matter where the "hub." params are added? >> >> Cheers, >> > >
