Skip to content
This repository
Browse code

Fixing location in explanation of example. @slact, shouldn't line 153

read "push_subscriber with this id is *NOT* presently connected"? I'm
not sure this functionality is working correctly actually, but just
trying to suss out what's intended.
  • Loading branch information...
commit bc71bb733e38a644a75d2ba68690f79fb98bd24d 1 parent 369fa91
Carson Baker authored October 31, 2009 slact committed November 05, 2009

Showing 1 changed file with 3 additions and 3 deletions. Show diff stats Hide diff stats

  1. 6  README
6  README
@@ -143,14 +143,14 @@ http {
143 143
 
144 144
 ---------------------------- Operation ---------------------------------------
145 145
 Assuming the example config given above:
146  
-Clients will connect to http://example.com/listen?id=... and have the 
147  
-response delayed until a message is POSTed to http://example.com/send?id=...
  146
+Clients will connect to http://example.com/activity?id=... and have the 
  147
+response delayed until a message is POSTed to http://example.com/publish?id=...
148 148
 Messages can be sent to clients that have not yet connected, i.e. they are 
149 149
 queued.
150 150
 
151 151
 Upon sending a request to a push_publisher location, the server will respond with 
152 152
 a 201 Created if the message has been sent. If it must be queued up (i.e. the 
153  
-push_subscriber with this id is presently connected), a 202 Accepted will be sent.
  153
+push_subscriber with this id is not presently connected), a 202 Accepted will be sent.
154 154
  
155 155
 If you intend to have the publisher be a server-side application, 
156 156
 it's a damn good idea to make sure the push_publisher location is not visible

0 notes on commit bc71bb7

Please sign in to comment.
Something went wrong with that request. Please try again.