Hi,
While transfering a file using smack api . i am getting
outgoingtransfer.isdone() value is true but getStatus() is error . i am
using asmack-2010.04.02.jar for android. i am trainign to send the file
from android to android


On Thu, Jun 27, 2013 at 5:30 PM, <[email protected]> wrote:

> Send Standards mailing list submissions to
>         [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://mail.jabber.org/mailman/listinfo/standards
> 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 Standards digest..."
>
>
> Today's Topics:
>
>    1. NEW: XEP-0331 (Data Forms - Color Field Types)
>       (XMPP Extensions Editor)
>    2. Updated Yabasta Protocol (E2E-related) (Jon Kristensen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 26 Jun 2013 15:43:25 +0000
> From: XMPP Extensions Editor <[email protected]>
> To: [email protected]
> Subject: [Standards] NEW: XEP-0331 (Data Forms - Color Field Types)
> Message-ID: <[email protected]>
>
> Version 0.1 of XEP-0331 (Data Forms - Color Field Types) has been released.
>
> Abstract: This specification defines how to publish fields in data forms
> that take color values. Color values are best edited using a color picker
> dialog, rather than manual input.
>
> Changelog: Initial published version approved by the XMPP Council. (psa)
>
> Diff: N/A
>
> URL: http://xmpp.org/extensions/xep-0331.html
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 26 Jun 2013 20:16:21 +0200
> From: Jon Kristensen <[email protected]>
> To: [email protected]
> Subject: [Standards] Updated Yabasta Protocol (E2E-related)
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="UTF-8"
>
> Hello everyone!
>
> The OTR-inspired and end-to-end secure Yabasta protocol has received a
> significant update today. You can see the updated protocol at
> <https://github.com/jonkri/yabasta-protocol/>.
>
> The protocol now supports a higher degree of anonymity than it did
> before. The public key is no longer automatically transferred in the
> authenticated key exchange (as is the case with the Off-the-Record
> protocol). Instead, the key exchange only exposes a signature. Users can
> then perform various identity verification actions (such as
> "challenges") to increase their trust in the remote peer before they
> reveal their public key. This is done so that clients can choose to
> consider their public keys a secret credential, and not automatically
> reveal their public keys to an active man-in-the-middle attacker.
>
> The protocol has also been made more flexible. Clients can now configure
> things like what prime numbers to use for the Diffie-Hellman
> calculations, as well as what cryptographic and signing algorithms to
> use. Other updates include a separation between the abstract method and
> the actual protocol implementation, various clean-ups, and additional
> explanations to make the document easier to understand.
>
> Feedback is more than welcome! :-)
>
> Thanks!
>
> Jon Kristensen
>
>
>
> ------------------------------
>
> _______________________________________________
> Standards mailing list
> [email protected]
> http://mail.jabber.org/mailman/listinfo/standards
>
>
> End of Standards Digest, Vol 115, Issue 33
> ******************************************
>



-- 
Thanks & Regards,
CH.sravani.

Reply via email to