CloudServices/Notifications/Push/API: Difference between revisions

CloudServices/Notifications/Push/API (view source)

261 bytes added , 5 February 2012

Confirmed users

591

edits

@@ Line 99: / Line 99: @@
 JSON blobs and form-urlencoded parameters.
-<i><pre>
+HTTP Status Codes:
+* '''200''': Notification accepted for delivery
+* '''404''': We don't have that URL in our database
+* '''410''': The user isn't receiving these notifications, e.g. access was revoked
+To support bulk sends, we may be able to use SPDY to get longer-lived connections sending
+a bunch of requests while still keeping the same HTTP interface.
+= Feedback =
+<i>
+<pre>
 (No feedback mechanism is listed, so I'm putting it here; feel free to point me elsewhere :-)
 -- Is the "body" plain text or HTML, or something else?
@@ Line 115: / Line 127: @@
 -- How does this handle a user who uses two different Web browsers? (e.g. IE at work and Firefox at home)
-Hixie</pre></i>
+Hixie</pre>
-HTTP Status Codes:
+<blockquote>
+* How is the privacy impact of following the user (IP addresses, usage times) reduced to the absolute minimum possible?
+* Why the middle man Mozilla? Decentralization is a core principle of the Internet.
+Ben Bucksch
+</blockquote>
-* '''200''': Notification accepted for delivery
+</i>
-* '''404''': We don't have that URL in our database
-* '''410''': The user isn't receiving these notifications, e.g. access was revoked
-To support bulk sends, we may be able to use SPDY to get longer-lived connections sending
-a bunch of requests while still keeping the same HTTP interface.