<div dir="ltr">Hi,<br>As Michael told its complete correct, and as you were searching for gauranteed delivery i'll provide you with some information<br><br>In that extension it provides you with the delivery of the message is done or not. with some status. So with that you can track the delivery.<br>
<br>And Applications is always ON, the connection with the server will always be connected until you close the application in other sense until you interrupt the connectivity with the server. Because usually XMPP Framework sends the ping to the server at regular intervals if there is any update on the server side or client side.<br>
<br>And I'm not expert but trying to become expert.<br><br><div class="gmail_quote">On Tue, Nov 13, 2012 at 10:20 AM, andy nes <span dir="ltr"><<a href="mailto:andynes83@gmail.com" target="_blank">andynes83@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey Michael,<div><br></div><div>Thank you for a quick reply, appreciate it.</div><div><br></div><div>Guaranteed Message Delivery is quite important for us. Shall look into the XEP.</div>
<div><br></div><div>Also, we are inclined towards ejabberd as server. Will check if ejabberd implements <span style="font-family:arial,sans-serif;font-size:13px">XEP-184.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">I realized that Machine to Machine requirement is redundant, can ignore that.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Always ON: The application is a tracking one. Hence the application should always, at regular intervals, send the location data to the server without closing the connection. The application runs on a mobile. That's what I mean by Always ON.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Any idea if there's any XEP for stream compression?</span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div><div><font face="arial, sans-serif">regards,</font></div><div><font face="arial, sans-serif">andy</font></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Nov 13, 2012 at 12:42 PM, Michael Weibel <span dir="ltr"><<a href="mailto:michael.weibel+xmpp@gmail.com" target="_blank">michael.weibel+xmpp@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi andy,<br>
<br>
> Real time communication.<br>
<br>
You'll get that for free when you open a connection to the XMPP Server.<br>
<br>
> Push based communication.<br>
<br>
Besides ejabberd commercial, I don't know which servers implement this.<br>
<br>
> Guaranteed message delivery<br>
<br>
This is one of the most important things for mobile (as you might know already). There's XEP-184[1] for this and you have to watch out that your server implements this in order to know that the server really received this message.<br>
Besides this XEP there exist different implementations by some servers.<br>
<br>
> Scalability<br>
<br>
This entirely depends on the server and, more specifically on your use case. You might want to do load tests using e.g. Tsung[2].<br>
<br>
> Machine to Machine communication<br>
<br>
What do you mean with this? XMPP is a federated protocol, therefore S2S communication is builtin.<br>
<br>
> Mobile friendly<br>
<br>
XML is considered verbose. You can enable stream compression if the server supports it. On the last XMPP Summit they talked about XML->JSON translating which might help to reduce verbosity.<br>
<br>
> always on<br>
<br>
I don't know what you mean with this, can you elaborate?<br>
<div><br>
> Is XMPP good to build a Mobile app?<br>
<br>
</div>Message reliability is very important (as said previously). Also you'll need an XMPP library which is robust. There's e.g. asmack[3] for Android and e.g. XMPPFramework[4] for iOS.<br>
<br>
Hope this helps,<br>
Michael<br>
<br>
[1]: <a href="http://xmpp.org/extensions/xep-0184.html" target="_blank">http://xmpp.org/extensions/xep-0184.html</a><br>
[2]: <a href="http://tsung.erlang-projects.org/" target="_blank">http://tsung.erlang-projects.org/</a><br>
[3]: <a href="https://github.com/rtreffer/asmack" target="_blank">https://github.com/rtreffer/asmack</a><br>
[4]: <a href="https://github.com/robbiehanson/XMPPFramework" target="_blank">https://github.com/robbiehanson/XMPPFramework</a><br>
_______________________________________________<br>
JDev mailing list<br>
Info: <a href="http://mail.jabber.org/mailman/listinfo/jdev" target="_blank">http://mail.jabber.org/mailman/listinfo/jdev</a><br>
Unsubscribe: <a href="mailto:JDev-unsubscribe@jabber.org" target="_blank">JDev-unsubscribe@jabber.org</a><br>
_______________________________________________<br>
</blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
JDev mailing list<br>
Info: <a href="http://mail.jabber.org/mailman/listinfo/jdev" target="_blank">http://mail.jabber.org/mailman/listinfo/jdev</a><br>
Unsubscribe: <a href="mailto:JDev-unsubscribe@jabber.org">JDev-unsubscribe@jabber.org</a><br>
_______________________________________________<br>
<br></blockquote></div><br></div>