Hi,
Is there any possiblity to implement Push at iPhone Client if we know the DeviceToken. Why we cannot go for a client side Push Implementation ? And if we have cert as .p12 on client Documents Directory
Tharindu.
Hi,
Is there any possiblity to implement Push at iPhone Client if we know the DeviceToken. Why we cannot go for a client side Push Implementation ? And if we have cert as .p12 on client Documents Directory
Tharindu.
Well that comment really makes it clear. Your orignal question wasn't. Yes certificate experation can be an issue. You could deal with it by ensuring you send out updates to your app before every expiration, or you could host your cert and the apps check the cert experation date for the cert they have and if its near the end it will poll your server to download the new one. This raises more issues. By allowing your cert to be downloaded someone could more easily get it and start pushing using your identity. But even if you bundle the cert in the app its easy for somone to extract, so I'd recommend against it. Use a server, and have a client send a request to that server to notify another client. That way only your privatly managed code/site is sending the actual push notifications, and you can always stop sending if someone starts spamming push requests. If its all client side they could spam notifications until Apple pulled the plug. If Apple has to do that they would block you from sending push since it was your cert doing the spamming.
So why do you think you shouldn't use a server? If you are just trying to avoid having to set up a server and code it, you have no valid reason.
I would assume Apple would watch the network communications from an app to and from its push servers, and they should easily catch this. It wouldn't shock me at all if they won't approve it this way.
It's possible to do it but most people don't for security reasons. Someone could get your binary, extract the cert. and push out their own notifications.