4 ms·
Sweet. Now accepting pull requests :) Interesting. We haven't hit that issue yet. Hmmm. We also haven't had any issues with feedback affecting our outgoing me
by vanstee 14y ago
Sweet. Now accepting pull requests :)
Interesting. We haven't hit that issue yet.
Hmmm. We also haven't had any issues with feedback affecting our outgoing messages. Yeah we just check for messages from the feedback socket after sending a notification (as Apple's guide recommends) but we're not doing anything fancy like waiting for a response. Sounds cool though.
- kyledrake 14y agoI want to remove the IO.select because it slows things down unfortunately. I noticed you are using enhanced push, but also opening a feedback socket separately. I was under the impression that you were supposed to read feedback in-line with the enhanced protocol, but I may have gotten this wrong. Are you using the enhanced protocol -and- listening to the feedback socket? This is interesting, and may solve a problem I'm having, so I wanted to get your thoughts.
- vanstee 14y agoCouldn't find that in the guide (reading feedback from the same socket). I might have missed it though. And yep. We're using the enhanced protocol while opening another connection to the feedback service. I just followed this section of the docs. http://developer.apple.com/library/mac/#documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/CommunicatingWIthAPS/CommunicatingWIthAPS.html#//apple_ref/doc/uid/TP40008194-CH101-SW3 http://developer.apple.com/library/mac/#documentation/Networ...
- deleted 14y ago[deleted]
- kyledrake 14y agoWhere do you call the feedback socket after sending a notification in the code? Is this something you do on your application's end? Sorry, last question I promise. Pull requests coming soon!
- vanstee 14y agoOh sorry. Yeah we do this in our app (not automatically in the gem).