|
If you were logged in you would be able to see more operations.
|
|
|
Smack
Created: 06/16/06 04:37 PM
Updated: 09/14/06 02:15 PM
|
|
| Component/s: |
Core
|
| Affects Version/s: |
2.2.0
|
| Fix Version/s: |
3.0.0 Beta 1
|
|
|
Time Tracking:
|
|
Original Estimate:
|
3 days
|
|
|
Remaining Estimate:
|
3 days
|
|
|
Time Spent:
|
Not Specified
|
|
|
|
| Support Plan Customer Issue: |
No
|
| Resolution Date: |
09/14/06 02:15 PM
|
| Acceptance Test - Add?: |
No
|
Update the XMPP Error in order to implement the RFC3920 chapter 9.3 ( http://www.xmpp.org/specs/rfc3920.html#stanzas-error ).
The XMPP Error will have a code, condition and type:
- The code remainds the same as today.
- There will be some conditions by default (like item-not-found) and users may create errors using them or new ones.
- Available types will be: wait, cancel, modify auth and continue.
The new way to create errors will be using a condition and not a code.
|
|
Description
|
Update the XMPP Error in order to implement the RFC3920 chapter 9.3 ( http://www.xmpp.org/specs/rfc3920.html#stanzas-error).
The XMPP Error will have a code, condition and type:
- The code remainds the same as today.
- There will be some conditions by default (like item-not-found) and users may create errors using them or new ones.
- Available types will be: wait, cancel, modify auth and continue.
The new way to create errors will be using a condition and not a code. |
Show » |
| There are no comments yet on this issue.
|
|
Improvement
Closed
Minor
Update the XMPPError to be compliant with RFC3920