1. COMET notifications-only server
2. browser must query source for actual data, not brokered by Spark
3. short and long cycle
1. reconnect per message and wait
2. long lived connection (must get callback in browser)
4. piggybacking
1. get all scope at once, not just single notification
2. get scope back when making unrelated queries
5. URL only, no data push
6. connection returns identity
1. <URL>
2. assigned at connect
7. select(), not threads
8. write to <URL>/11A2 on event written to connection with that ID
9. <URL>/<PATH>/<SCOPE>/?id=11A2&t=<TIME>
1. timestamp
10. broadcast groups?
1. <URL>/<PATH>/<SCOPE>/?amp;t=<TIME>
2. sent to all matching, id parameter inserted by Spark
Original issue reported on code.google.com by dbsha...@gmail.com on 24 Sep 2009 at 9:08
Original issue reported on code.google.com by
dbsha...@gmail.com
on 24 Sep 2009 at 9:08