4 ms·

I'm aware of Apple's sample code, I attended the WWDC talk on integrating Push Notifications. I'm just not aware of many Ruby developers interested in taking Ap

I'm aware of Apple's sample code, I attended the WWDC talk on integrating Push Notifications. I'm just not aware of many Ruby developers interested in taking Apple's C example and implementing it in Ruby. HTTP POST is simpler for the developer. TCP is better for Apple. Apple has the resources to scale, so "TCP is faster" isn't really an excuse, in my ostensibly professional opinion.

deleted 15y ago
[deleted]
Rusky 15y ago
Apple has the resources to scale, so "TCP is faster" isn't really an excuse Really? HTTP is just sending lines of text over TCP- what's so hard about a binary format instead? In many ways it's easier. You shouldn't need an excuse to remove unnecessary layers of translation.
- AshFurrow 15y ago
  For a hobby developer or small business where time is precious, using built-in HTTP libraries is far easier and faster than implementing this: http://developer.apple.com/library/mac/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Art/aps_provider_binary.jpg http://developer.apple.com/library/mac/documentation/Network... Sorry, but you're not going to convince me that rolling your own implementation of Apple's APNS is better than an HTTP-based APNS would have been.
  - nupark2 15y ago
    > For a hobby developer or small business where time is precious, using built-in HTTP libraries is far easier and faster ... Sorry, but you're not going to convince me that rolling your own implementation of Apple's APNS is better than an HTTP-based APNS would have been. Something is rotten in the state of Denmark; if this can be done in 20 lines of Python (see comment above), then why do so many ostensibly capable engineers find it so difficult?
    - AshFurrow 15y ago
      Sorry, you may have just not heard me before: > I'm just not aware of many Ruby developers interested in taking Apple's C example and implementing it in Ruby. I don't find it difficult; I find it more difficult than a simple POST.
      - nupark2 15y ago
        In which case the failure to communicate is mutual; In OP, I said: ... this position drives me bonkers ("not HTTP, too hard")! As professional engineers, it's my hope that opening up a persistent TCP socket and sending a small, stateless binary message should be easier, faster to implement, and better performing than marshaling everything into HTTP (for no other reason than HTTP is more familiar to you!). If that's not the case, then I would strongly recommend that any engineers that are uncomfortable with this simple task should review UNIX Network Programming Vol 1, and Network Security with OpenSSL, rather than complain that an HTTP interface isn't available. At the very least, such a study would provide a necessary understanding of what HTTP is doing. With that in place, opening up a connection to APNS should be a walk in the park.
  - Rusky 15y ago
    Parsing a byte and two length-prefixed strings is harder than a text-based protocol? I'm having a hard time believing anyone could think that.
    - Someone 15y ago
      I may be too cynical, but I think there are zillions of programmers who do not know what network byte order is, or even what a byte is. If you work on server-side stuff on the back-end of some web app, you do not really need (for some definition of 'need'h to know either.

deleted 15y ago

[deleted]

Rusky 15y ago

Apple has the resources to scale, so "TCP is faster" isn't really an excuse Really? HTTP is just sending lines of text over TCP- what's so hard about a binary format instead? In many ways it's easier. You shouldn't need an excuse to remove unnecessary layers of translation.

AshFurrow 15y ago
For a hobby developer or small business where time is precious, using built-in HTTP libraries is far easier and faster than implementing this: http://developer.apple.com/library/mac/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Art/aps_provider_binary.jpg http://developer.apple.com/library/mac/documentation/Network... Sorry, but you're not going to convince me that rolling your own implementation of Apple's APNS is better than an HTTP-based APNS would have been.
- nupark2 15y ago
  > For a hobby developer or small business where time is precious, using built-in HTTP libraries is far easier and faster ... Sorry, but you're not going to convince me that rolling your own implementation of Apple's APNS is better than an HTTP-based APNS would have been. Something is rotten in the state of Denmark; if this can be done in 20 lines of Python (see comment above), then why do so many ostensibly capable engineers find it so difficult?
  - AshFurrow 15y ago
    Sorry, you may have just not heard me before: > I'm just not aware of many Ruby developers interested in taking Apple's C example and implementing it in Ruby. I don't find it difficult; I find it more difficult than a simple POST.
    - nupark2 15y ago
      In which case the failure to communicate is mutual; In OP, I said: ... this position drives me bonkers ("not HTTP, too hard")! As professional engineers, it's my hope that opening up a persistent TCP socket and sending a small, stateless binary message should be easier, faster to implement, and better performing than marshaling everything into HTTP (for no other reason than HTTP is more familiar to you!). If that's not the case, then I would strongly recommend that any engineers that are uncomfortable with this simple task should review UNIX Network Programming Vol 1, and Network Security with OpenSSL, rather than complain that an HTTP interface isn't available. At the very least, such a study would provide a necessary understanding of what HTTP is doing. With that in place, opening up a connection to APNS should be a walk in the park.
- Rusky 15y ago
  Parsing a byte and two length-prefixed strings is harder than a text-based protocol? I'm having a hard time believing anyone could think that.
  - Someone 15y ago
    I may be too cynical, but I think there are zillions of programmers who do not know what network byte order is, or even what a byte is. If you work on server-side stuff on the back-end of some web app, you do not really need (for some definition of 'need'h to know either.