PFS2: Difference between revisions

PFS2 (view source)

Revision as of 21:57, 1 September 2009

353 bytes added , 1 September 2009

Adding more info

Aking

Confirmed users

1,136

edits

@@ Line 1: / Line 1: @@
+= Server =
+== Codebase ==
+http://svn.mozilla.org/projects/pfs2/trunk/
 == Schema ==
 * [http://svn.mozilla.org/addons/trunk/site/app/config/sql/remora.sql Checked in here]
@@ Line 4: / Line 8: @@
 * mimes
 * plugins_mimes
+== Environments ==
+Dev - local
 == Request ==
@@ Line 24: / Line 31: @@
   appABI=x86-gcc3
   locale=en-US
+PFS 2 Example call - GET to:
+  http://pfs2.mozilla.org/?appID={ec8030f7-c20a-464f-9b0e-13a3a9e97384}&mimetype=application/x-shockwave-flash&appVersion=2008052906&appRelease=3.0&clientOS=Windows%20NT%205.1&chromeLocale=en-US&callback=later
+* callback - optional, makes the output JSONP instead of JSON
 == Response ==
@@ Line 54: / Line 66: @@
   } ]
-= Q&A =
+= Client =
-* What is the API for a request in PFS2?
+== Codebases ==
-** Will add this to the "request" section but it will look a lot like a cross between the extension update service and the URLs used for PFS currently
+* [http://svn.mozilla.org/projects/mozilla.com/ mozilla.com]
-* Is it a GET with query string like [[PFS]], or is it a POST with a JSON encoded body (like one below with less info)?
+* [http://github.com/ozten/Perfidies-of-the-Web/tree Perfidies of the Web]
-** I think it's pretty easy to handle either case, but since we'd potentially be dealing with arrays of plugins I'd opt to accept a JSON body and have the app run logic on it.
-** One argument against using POST is that doing so doesn't give you a good cache hit rate and could possibly crush the service doing operations that otherwise could be easily cached (albeit with an increase in HTTP requests).
+Perfidies is the PFS2 client. It will be usable for plugin page, web badges, etc.
-* Will there be a batch request mode, or 1 request per plugin?
-** Leaning towards 1 request per plugin at this point, but we should take some time to figure out which solution is best.
+== PFS2 inputs ==
+* App ID is hardcoded in the JS. We'll update this script when a new appId is available. Firefox always uses the same app id and it won't change any time soon.
+* appID={ec8030f7-c20a-464f-9b0e-13a3a9e97384}
+* mimetype - navigator.plugins[x].type roughly
+* appVersion = navigator.buildid roughly
+* appRelease = navigator.appVersion roughly
+* clientOS = navigator.oscpu roughly
+* chromeLocale = navigator.language
+== Environments ==
+* dev - I have a dev instance up
+* trunk - https://www-trunk.stage.mozilla.com/
+* stage - https://www.authstage.mozilla.com/
+* prod - http://www.mozilla.com/

PFS2: Difference between revisions

PFS2 (view source)

Revision as of 21:57, 1 September 2009

Navigation menu

Search