I suspect I'll just be sending one of the names in this list: ["Wikipedia (en)", "Bing", "eBay", "Creative Commons", "Answers.com", "Amazon.com", "Yahoo", "Google"] but accepting any string (for extensibility) seems like a good idea. Thanks, Blake.
SOomething like : https://opensearch.live.mozillamessaging.com/search/google?q=[xxxx] => http://www.googe.com/search?q=[xxxx] And really, internally we'd have mappings like: /google => http://www.google.com/search And pass everything else along, right ??
we decided to take pings with a get parameter, return 206, use access logs to store metrics, everyone wins!
(In reply to comment #2) > we decided to take pings with a get parameter, return 206, use access logs to > store metrics, everyone wins! Can we agree on the format of these pings ?
Sure, Pick something, and I'll code that up. (I figured it would be along the lines of http://…/…?provider=<XXX> ) Later, Blake.
(I asked Sancus, and he said he can't do it, so I'm assigning it to you so that it doesn't get lost. Also, we're hoping to release the add-on next week, so getting this up soon would be good.)
Assignee: nobody → gozer
Status: NEW → ASSIGNED
$> lwp-request -m GET -esS http://opensearch.live.mozillamessaging.com/search?provider=google GET http://opensearch.live.mozillamessaging.com/search?provider=google --> 204 No Content Connection: close Date: Thu, 10 Feb 2011 21:17:28 GMT Via: 1.1 varnish Age: 0 Server: Apache/2.2.3 (CentOS) Content-Length: 0 Content-Type: text/plain; charset=UTF-8 Client-Date: Thu, 10 Feb 2011 21:17:28 GMT Client-Peer: 22.214.171.124:80 Client-Response-Num: 1 X-Varnish: 2943614467
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.