Chat Client *PUSH*

---

Hi,

Was wondering is there a decent IM chat client that supports push on the android? i was looking around and didn't find anything.

Originally Posted by huzz

Hi,

Was wondering is there a decent IM chat client that supports push on the android? i was looking around and didn't find anything.

there area a couple.eBuddy, palringo, Hi Yahoo, Agile mesenger.

Originally Posted by Henchman

there area a couple.eBuddy, palringo, Hi Yahoo, Agile mesenger.

They support push? coz i couldn't see anything in the settings must be going blind, will check. Thanks.

Originally Posted by huzz

They support push? coz i couldn't see anything in the settings must be going blind, will check. Thanks.

when you say push, you mean immediate sending and receiving of messages?
If so, then that's exactly what they do.

Originally Posted by Henchman

when you say push, you mean immediate sending and receiving of messages?
If so, then that's exactly what they do.

http://en.wikipedia.org/wiki/Push_technology

Immediate sending and receiving is not PUSH. Basically if you are signed on and even if the application is closed you will receive notification of the message sent. Just like how Gmail works instead of email though this is related to IM chat.

I suspect that the way you're using the term 'push' here is a reference to Apple's oh-hell-no-we-won't-allow-multitasking-but-here's-a-polished-dog-turd way of letting apps receive out of band notifications without leaving them running.

This isn't necessary on Android, as it supports multitasking - applications can mark their threads as backgroundable. Most IM apps will, therefore, keep running their network code in the background meaning you can get messages all the time. A good indicator whether this is the case is if the application has an 'Exit' or 'Quit' option in its menu.

Blah blah blah Android > iPhone blah blah blah

Thank you. I understand better.

Originally Posted by dave-on-android

I suspect that the way you're using the term 'push' here is a reference to Apple's oh-hell-no-we-won't-allow-multitasking-but-here's-a-polished-dog-turd way of letting apps receive out of band notifications without leaving them running.

This isn't necessary on Android, as it supports multitasking - applications can mark their threads as backgroundable. Most IM apps will, therefore, keep running their network code in the background meaning you can get messages all the time. A good indicator whether this is the case is if the application has an 'Exit' or 'Quit' option in its menu.

Blah blah blah Android > iPhone blah blah blah

Sorry, but no. Running the network code in the background uses up ram and battery life that having built in push support doesn't use. Every mobile OS beside Android supports push for IM services on some application, and it's a pretty ****ty situation for Android.

Originally Posted by Casao

Sorry, but no. Running the network code in the background uses up ram and battery life that having built in push support doesn't use. Every mobile OS beside Android supports push for IM services on some application, and it's a pretty ****ty situation for Android.

Running a push client eats battery life as well, doesn't it.
And I'm sure there us still a service running in the background to deal with the push client as well.
All using RAM, resources and battery power.
The reason these other phones run longer like sidekicks etc, us because they're not running a 1ghz minicomputer with powerful graphics capabilities.
My battery last as long as my daughters iPhone.

Other than the fact that to get push notifications in the first place, there needs to be...network code running in the background.

Some apps chew more data than others, sure. That's a case of bad code, not bad OS design. If you're setting up lots of processor and network intensive stuff in a Service, you're doing it wrong.

Denying developers and users the ability to run anything in the background goes down the iPhone route - and that way madness lies.