News for hackers. Stuff that matters.

A comment on Google yanks sketchy iMessage clone for Android from app store. Parent comment

Re:Google yanks sketchy iMessage clone for Android from app ... by lnanek2 on Sunday September 29, 2013 @08:34AM (#6465003)
This is very standard with web scraping implementations. Honestly, if you are reversing someone's protocol or scraping their web site, you are stupid if you put the implementation on the client because it will break all the time. Instead you put it on a server where you can fix breaks instantly. The server usually delays/shows stale data while things are broken as well, then does what it can to replay once fixed.
[ Parent | on HN ]
Re:Google yanks sketchy iMessage clone for Android from app ... by elyase on Sunday September 29, 2013 @10:28AM (#6465244)
On the other hand putting things on the server means that you can get cut (by IP) and also brings the need of dealing with scaling problems.
[ Parent | on HN ]
Re:Google yanks sketchy iMessage clone for Android from app ... by toomuchtodo on Sunday September 29, 2013 @12:33PM (#6465603)
You can always scale easier on the server platform, as well as spin up new instances with new IPs on any VM platform.

Handling it on the server allows you some control over the chaos. Not so much when all the logic is on your mobile app.

[ Parent | on HN ]
Re:Google yanks sketchy iMessage clone for Android from app ... by marcc on Sunday September 29, 2013 @01:15PM (#6465769)
You aren't suggesting that it scales easier on the server than on the mobile client, are you? Nothing would scale better for this app than putting the logic on the client -- it's a customer's phone communication with an Apple server. This leaves nothing for him to scale, anywhere, except for engineering to push out updates.
[ Parent | on HN ]
Re:Google yanks sketchy iMessage clone for Android from app ... by toomuchtodo on Sunday September 29, 2013 @01:43PM (#6465889)
I wouldn't say you're scaling properly if you have millions of mobile clients failing to make the proper calls to a service because the protocol has been changed. I'd say its damn near irresponsible to do that. It's not scaling if you're just throwing packets against the wall when the protocol or service unexpectedly changes.
[ Parent | on HN ]
Re:Google yanks sketchy iMessage clone for Android from app ... by sil3ntmac on Sunday September 29, 2013 @12:53PM (#6465691)
The impression I got was that actual requests and responses are still made by the client.
[ Parent | on HN ]
Re:Google yanks sketchy iMessage clone for Android from app ... by inafewwords on Sunday September 29, 2013 @12:55PM (#6465695)
>stupid if you put the implementation on the client because it will break all the time

Makes some sense to do Apk downloads for this unusual implementation of it allows a fix push

[ Parent | on HN ]