It does seem a bit odd, unless the parameters represent a specific preference order (as with the verify mode), the parameter order shouldn't denote anything specific. I think something I use here (as a subscriber sending non-standard parameters) is simply to byte order them (roughly alphabetically). This is done primarily to maintain a consistent order in case users decide to start meddling with HMACs, so maybe it's not all a bad idea for future proofing?
Paddy Pádraic Brady http://blog.astrumfutura.com http://www.survivethedeepend.com OpenID Europe Foundation Irish Representative ________________________________ From: Julien Genestoux <[email protected]> To: Pubsubhubbub <[email protected]> Sent: Sun, January 24, 2010 11:44:25 AM Subject: [pubsubhubbub] Appding query straing parameters at the end? 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,
