<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.7" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Battle for Mobile Instant Messaging</title>
	<link>http://hip2b2.yutivo.org/2006/03/06/battle-for-mobile-instant-messaging/</link>
	<description>Mobile, Security, Web 2.0, Pipe Dreams and More</description>
	<pubDate>Sun, 20 May 2012 10:20:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.7</generator>

	<item>
		<title>by: It&#8217;s hip2b2 (Mobile, Security, Web 2.0, Pipe Dreams and More) &#187; Blog Archive &#187; OMA IMPS Why Bother?</title>
		<link>http://hip2b2.yutivo.org/2006/03/06/battle-for-mobile-instant-messaging/#comment-585</link>
		<pubDate>Wed, 18 Oct 2006 01:23:01 +0000</pubDate>
		<guid>http://hip2b2.yutivo.org/2006/03/06/battle-for-mobile-instant-messaging/#comment-585</guid>
					<description>[...] So with these three (3) simple reasons (of course, there are more) alone, it is pretty clear that support OMA IMPS is still important if an IM provider would like to penetrate the mobile phone network market. For more discussion on the existing open standards IMPS protocols, check out this previous blog of mine. I also did a comparison between SIP/SIMPLE and XMPP. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] So with these three (3) simple reasons (of course, there are more) alone, it is pretty clear that support OMA IMPS is still important if an IM provider would like to penetrate the mobile phone network market. For more discussion on the existing open standards IMPS protocols, check out this previous blog of mine. I also did a comparison between SIP/SIMPLE and XMPP. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Migs</title>
		<link>http://hip2b2.yutivo.org/2006/03/06/battle-for-mobile-instant-messaging/#comment-105</link>
		<pubDate>Tue, 23 May 2006 12:57:58 +0000</pubDate>
		<guid>http://hip2b2.yutivo.org/2006/03/06/battle-for-mobile-instant-messaging/#comment-105</guid>
					<description>Now that I'm reading through the IMPS spec, more inputs:
1. IMPS is very flexible in specifying client capabilities.
2. IMPS can degrade to low bandwidth conditions.
3. IMPS (in my opinion) has a revenue environment in mind, while the others assume a "free" scheme.</description>
		<content:encoded><![CDATA[<p>Now that I&#8217;m reading through the IMPS spec, more inputs:<br />
1. IMPS is very flexible in specifying client capabilities.<br />
2. IMPS can degrade to low bandwidth conditions.<br />
3. IMPS (in my opinion) has a revenue environment in mind, while the others assume a &#8220;free&#8221; scheme.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: wyuwp</title>
		<link>http://hip2b2.yutivo.org/2006/03/06/battle-for-mobile-instant-messaging/#comment-53</link>
		<pubDate>Fri, 14 Apr 2006 07:11:12 +0000</pubDate>
		<guid>http://hip2b2.yutivo.org/2006/03/06/battle-for-mobile-instant-messaging/#comment-53</guid>
					<description>good case against XMPP. 

but, SIP/SIMPLE is also a clean protocol based on HTTP. actually, it is even simpler than OMA IMPS (formerly WV). why not SIP/SIMPLE? since push-to-talk is probably VoIP'sh already.</description>
		<content:encoded><![CDATA[<p>good case against XMPP. </p>
<p>but, SIP/SIMPLE is also a clean protocol based on HTTP. actually, it is even simpler than OMA IMPS (formerly WV). why not SIP/SIMPLE? since push-to-talk is probably VoIP&#8217;sh already.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Migs</title>
		<link>http://hip2b2.yutivo.org/2006/03/06/battle-for-mobile-instant-messaging/#comment-52</link>
		<pubDate>Fri, 14 Apr 2006 04:02:53 +0000</pubDate>
		<guid>http://hip2b2.yutivo.org/2006/03/06/battle-for-mobile-instant-messaging/#comment-52</guid>
					<description>I have a theory on why OMA IMPS is favored over XMPP by some vendors. 

It uses HTTP, which is well-supported by mobile data gateways and is request/response based. 

XMPP on the other hand uses a different TCP port and keeps the connection open - not wire(less)-friendly.</description>
		<content:encoded><![CDATA[<p>I have a theory on why OMA IMPS is favored over XMPP by some vendors. </p>
<p>It uses HTTP, which is well-supported by mobile data gateways and is request/response based. </p>
<p>XMPP on the other hand uses a different TCP port and keeps the connection open - not wire(less)-friendly.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: wyuwp</title>
		<link>http://hip2b2.yutivo.org/2006/03/06/battle-for-mobile-instant-messaging/#comment-44</link>
		<pubDate>Tue, 04 Apr 2006 04:30:29 +0000</pubDate>
		<guid>http://hip2b2.yutivo.org/2006/03/06/battle-for-mobile-instant-messaging/#comment-44</guid>
					<description>plain packetize as in BASE64 encode the data? that is interesting. but how do you do this and still keep XMPP compliance? or this portion is non-compliant?

also for OMA IMPS, how do you intend to support this? via JAIN or Parlay?</description>
		<content:encoded><![CDATA[<p>plain packetize as in BASE64 encode the data? that is interesting. but how do you do this and still keep XMPP compliance? or this portion is non-compliant?</p>
<p>also for OMA IMPS, how do you intend to support this? via JAIN or Parlay?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Roger D</title>
		<link>http://hip2b2.yutivo.org/2006/03/06/battle-for-mobile-instant-messaging/#comment-43</link>
		<pubDate>Tue, 04 Apr 2006 03:24:27 +0000</pubDate>
		<guid>http://hip2b2.yutivo.org/2006/03/06/battle-for-mobile-instant-messaging/#comment-43</guid>
					<description>Hi, 

we have implemented extensions/plugins in the open source XMPP. We have looked at JAIN before and we see future services for it and it is still in the concept stage. 

You can check out our mobile IM in this site, www.yehba.com. The one in the download site doesn't have the file transfer feature but in our lab and for the enterprise version we have it, yup it can MIME or just plain packetized payload. 

We are still studying the OMA IMPS specification and it will be good to have support on it.</description>
		<content:encoded><![CDATA[<p>Hi, </p>
<p>we have implemented extensions/plugins in the open source XMPP. We have looked at JAIN before and we see future services for it and it is still in the concept stage. </p>
<p>You can check out our mobile IM in this site, <a href="http://www.yehba.com." rel="nofollow">www.yehba.com.</a> The one in the download site doesn&#8217;t have the file transfer feature but in our lab and for the enterprise version we have it, yup it can MIME or just plain packetized payload. </p>
<p>We are still studying the OMA IMPS specification and it will be good to have support on it.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: wyuwp</title>
		<link>http://hip2b2.yutivo.org/2006/03/06/battle-for-mobile-instant-messaging/#comment-42</link>
		<pubDate>Mon, 03 Apr 2006 13:13:18 +0000</pubDate>
		<guid>http://hip2b2.yutivo.org/2006/03/06/battle-for-mobile-instant-messaging/#comment-42</guid>
					<description>hello,

i have heard you guys in the news before. so i presume that you are extending the Jabber open source XMPP server for your application? or are you using JAIN? or writing one from scratch?

i have yet to see your client but i presume that you use XMPP for communications between the mobile and the messaging and presence server?  how do you implement file transfers? SIP/SIMPLE and OMA WV do not provide IM file transfer. however, XMPP might since you can embed MIME content on it. is this accurate?

do you have plans of supporting OMA WV to allow most phone's built in presence and messaging clients to work?</description>
		<content:encoded><![CDATA[<p>hello,</p>
<p>i have heard you guys in the news before. so i presume that you are extending the Jabber open source XMPP server for your application? or are you using JAIN? or writing one from scratch?</p>
<p>i have yet to see your client but i presume that you use XMPP for communications between the mobile and the messaging and presence server?  how do you implement file transfers? SIP/SIMPLE and OMA WV do not provide IM file transfer. however, XMPP might since you can embed MIME content on it. is this accurate?</p>
<p>do you have plans of supporting OMA WV to allow most phone&#8217;s built in presence and messaging clients to work?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Roger D</title>
		<link>http://hip2b2.yutivo.org/2006/03/06/battle-for-mobile-instant-messaging/#comment-41</link>
		<pubDate>Mon, 03 Apr 2006 07:22:38 +0000</pubDate>
		<guid>http://hip2b2.yutivo.org/2006/03/06/battle-for-mobile-instant-messaging/#comment-41</guid>
					<description>Hi Hip2b2,

Our team have made the same study on what to use for our own Mobile IM implementation and decided to use XMPP on the server side. The system is versatile that it can also accomodate SIP/SIMPLE. While the client side on the mobile is our own protocol, this is due to the text that SIP generates for the signalling and XMPP is also a bloated protocol (XML). Since the mobile is using GPRS it will be expensive for the user, until the mobile operators decided to have gprs buffet meal, we'll stick to our protocol.</description>
		<content:encoded><![CDATA[<p>Hi Hip2b2,</p>
<p>Our team have made the same study on what to use for our own Mobile IM implementation and decided to use XMPP on the server side. The system is versatile that it can also accomodate SIP/SIMPLE. While the client side on the mobile is our own protocol, this is due to the text that SIP generates for the signalling and XMPP is also a bloated protocol (XML). Since the mobile is using GPRS it will be expensive for the user, until the mobile operators decided to have gprs buffet meal, we&#8217;ll stick to our protocol.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: It&#8217;s hip2b2 &#187; Blog Archive &#187; XMPP versus SIMPLE/SIP</title>
		<link>http://hip2b2.yutivo.org/2006/03/06/battle-for-mobile-instant-messaging/#comment-3</link>
		<pubDate>Mon, 06 Mar 2006 23:54:28 +0000</pubDate>
		<guid>http://hip2b2.yutivo.org/2006/03/06/battle-for-mobile-instant-messaging/#comment-3</guid>
					<description>[...] While browsing the Internet, I bumped into a Google Ad saying, &#8220;XMPP versus SIMPLE/IP&#8221;. This ad was sponsored by Jabber.com (which sells a commercial Jabber XMPP server). This is basically in relation to an article I wrote about Mobile Instant Messaging. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] While browsing the Internet, I bumped into a Google Ad saying, &#8220;XMPP versus SIMPLE/IP&#8221;. This ad was sponsored by Jabber.com (which sells a commercial Jabber XMPP server). This is basically in relation to an article I wrote about Mobile Instant Messaging. [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>

