[jdev] Help choosing the right technology

[Obaid Shaik]

Hi,
As Michael told its complete correct, and as you were searching for
gauranteed delivery i'll provide you with some information

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.

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.

And I'm not expert but trying to become expert.

On Tue, Nov 13, 2012 at 10:20 AM, andy nes <andynes83 at gmail.com> wrote:

> Hey Michael,
>
> Thank you for a quick reply, appreciate it.
>
> Guaranteed Message Delivery is quite important for us. Shall look into the
> XEP.
>
> Also, we are inclined towards ejabberd as server. Will check if ejabberd
> implements XEP-184.
>
> I realized that Machine to Machine requirement is redundant, can ignore
> that.
>
> 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.
>
> Any idea if there's any XEP for stream compression?
>
> regards,
> andy
>
>
> On Tue, Nov 13, 2012 at 12:42 PM, Michael Weibel <
> michael.weibel+xmpp at gmail.com> wrote:
>
>> Hi andy,
>>
>> > Real time communication.
>>
>> You'll get that for free when you open a connection to the XMPP Server.
>>
>> > Push based communication.
>>
>> Besides ejabberd commercial, I don't know which servers implement this.
>>
>> > Guaranteed message delivery
>>
>> 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.
>> Besides this XEP there exist different implementations by some servers.
>>
>> > Scalability
>>
>> 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].
>>
>> > Machine to Machine communication
>>
>> What do you mean with this? XMPP is a federated protocol, therefore S2S
>> communication is builtin.
>>
>> > Mobile friendly
>>
>> 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.
>>
>> > always on
>>
>> I don't know what you mean with this, can you elaborate?
>>
>> > Is XMPP good to build a Mobile app?
>>
>> 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.
>>
>> Hope this helps,
>> Michael
>>
>> [1]: http://xmpp.org/extensions/xep-0184.html
>> [2]: http://tsung.erlang-projects.org/
>> [3]: https://github.com/rtreffer/asmack
>> [4]: https://github.com/robbiehanson/XMPPFramework
>> _______________________________________________
>> JDev mailing list
>> Info: http://mail.jabber.org/mailman/listinfo/jdev
>> Unsubscribe: JDev-unsubscribe at jabber.org
>> _______________________________________________
>>
>
>
> _______________________________________________
> JDev mailing list
> Info: http://mail.jabber.org/mailman/listinfo/jdev
> Unsubscribe: JDev-unsubscribe at jabber.org
> _______________________________________________
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.jabber.org/jdev/attachments/20121113/61de6ac5/attachment-0001.html>