> On Sun, May 10, 2009 at 05:52:12PM +0800, ??? wrote:
>> As everybody know, the Mobile GPRS bandwidth is very sensitive, so the
>> scenario will be like this:
>> 1. Mobile Record the voice as one buffer or file in AMR codec.
>> 2. Client A, send this data to Client B ?maybe put the data into special
>> message stanza?, the data should be sent to the server first (as all message
>> will through server transfer to another client)
>> 3. The XMPP server will not directly send the data to Client B first,
>> but story the data, and notify the Client B, now there is one voice data
>> coming to you(including Client As's JID, time stamp, and maybe voice message
>> ID, etc)
>> 4. Client B if want to receive the voice message, then send the request
>> to the XMPP server, then the XMPP server will push the voice data to Client
>> B.
>
> Why store it on the server? Why not negotiate the ?do you want to get
> the message now?? with the other client and then use a file transfer to
> get it there?
>
> With regards
Hi Michal 'vorner' Vaner:
One thing is we don't want to Client to Client do the transfer voice
data or file
Because: 1. Some times the persion is not online
2. In GPRS connection,I think the P2P is not very
good solution for transfer the short voice message.
3. If use the server side, server side can setup the
Socket listen port,
and client can send the data to it fast as can
do the connection very fast.
but if use the P2P it will need some time to
setup the communication.
So we are thinking through the server side to transfer the voice data.
now we have the private IM application (include the client side and
server side), we're thinking go to XMPP.
The flow in our application now is as below:
1. First Client A setup the connection with Server, login
2. Get the list of friends, check the online frends, etc
3. Client A select one friend, chose send voice message
4. Start the voice record, voice will record as one AMR file
5. Send the AMR data to server
6. Server will check the destination user status, see wether it's
online or not.
7. If the dest-user online, server will send the notification to him,
"one voice message, do you want to receive? "
8. If it chose receive, then server will send the voice data to it.
9. All these communication base on socket communication.
So now we're finding the solution on XMPP.... how we can do? thanks
very much
Regards
Charles
----- Original Message -----
From: <[email protected]>
To: <[email protected]>
Sent: Monday, May 11, 2009 1:00 AM
Subject: JDev Digest, Vol 64, Issue 6
> Send JDev mailing list submissions to
> [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mail.jabber.org/mailman/listinfo/jdev
> or, via email, send a message with subject or body 'help' to
> [email protected]
>
> You can reach the person managing the list at
> [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of JDev digest..."
>
>
> Today's Topics:
>
> 1. Regarding XMPP Voice Message Processing (???)
> 2. Re: Regarding XMPP Voice Message Processing
> (Michal 'vorner' Vaner)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 10 May 2009 17:52:12 +0800
> From: ??? <[email protected]>
> Subject: [jdev] Regarding XMPP Voice Message Processing
> To: <[email protected]>
> Message-ID: <c8e9b77a43d44d71b8cbd892ceacc...@zsxcharles>
> Content-Type: text/plain; charset="gb2312"
>
> Hi All:
> We want to develop the IM application base on XMPP, and the Client
> application will run on the Mobile OS(such as Symbian, Windows Mobile, J2ME,
> etc).
> Now I am facing one problem about the voice message:
> We hope our application can send the voice message(like Voice SMS), from
> one client to another client through the Server, maybe we can encode the
> voice data to Base64.
> The server, we're planing to use OpenFire.
>
> As everybody know, the Mobile GPRS bandwidth is very sensitive, so the
> scenario will be like this:
> 1. Mobile Record the voice as one buffer or file in AMR codec.
> 2. Client A, send this data to Client B ?maybe put the data into special
> message stanza?, the data should be sent to the server first (as all message
> will through server transfer to another client)
> 3. The XMPP server will not directly send the data to Client B first, but
> story the data, and notify the Client B, now there is one voice data coming
> to you(including Client As's JID, time stamp, and maybe voice message ID, etc)
> 4. Client B if want to receive the voice message, then send the request to
> the XMPP server, then the XMPP server will push the voice data to Client B.
>
>
> This is our idea, but we didn't know how we can do and use which
> protocols. is anybody can help us. Thanks very much.
>
>
> Regards
> Charles
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <http://mail.jabber.org/pipermail/jdev/attachments/20090510/fe40afcd/attachment.html>
>
> ------------------------------
>
> Message: 2
> Date: Sun, 10 May 2009 12:32:39 +0200
> From: Michal 'vorner' Vaner <[email protected]>
> Subject: Re: [jdev] Regarding XMPP Voice Message Processing
> To: Jabber/XMPP software development list <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="utf-8"
>
> Hello
>
> On Sun, May 10, 2009 at 05:52:12PM +0800, ??? wrote:
>> As everybody know, the Mobile GPRS bandwidth is very sensitive, so the
>> scenario will be like this:
>> 1. Mobile Record the voice as one buffer or file in AMR codec.
>> 2. Client A, send this data to Client B ?maybe put the data into special
>> message stanza?, the data should be sent to the server first (as all message
>> will through server transfer to another client)
>> 3. The XMPP server will not directly send the data to Client B first,
>> but story the data, and notify the Client B, now there is one voice data
>> coming to you(including Client As's JID, time stamp, and maybe voice message
>> ID, etc)
>> 4. Client B if want to receive the voice message, then send the request
>> to the XMPP server, then the XMPP server will push the voice data to Client
>> B.
>
> Why store it on the server? Why not negotiate the ?do you want to get
> the message now?? with the other client and then use a file transfer to
> get it there?
>
> With regards
>
> --
> 2 keys should be enough for everyone
>
> Michal 'vorner' Vaner
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 198 bytes
> Desc: not available
> URL:
> <http://mail.jabber.org/pipermail/jdev/attachments/20090510/aa785dd5/attachment-0001.pgp>
>
> ------------------------------
>
> _______________________________________________
> JDev mailing list
> [email protected]
> http://mail.jabber.org/mailman/listinfo/jdev
>
>
> End of JDev Digest, Vol 64, Issue 6
> ***********************************
>
> __________ Information from ESET NOD32 Antivirus, version of virus signature
> database 4061 (20090507) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
_______________________________________________
JDev mailing list
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: [email protected]
_______________________________________________
