Use crd:error-code instead of security-error to express invalid account error |
||
Issue descriptionThis is a work item to move invalid account error from jingle security-error category into a single crd:error-code tag.
,
Jun 5 2016
X что за хрень?
,
Jun 7 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/d1ee82f8fe9fd81b8ecb6b668f0acf0fbaa262c2 commit d1ee82f8fe9fd81b8ecb6b668f0acf0fbaa262c2 Author: zijiehe <zijiehe@chromium.org> Date: Tue Jun 07 21:41:16 2016 [Chromoting]Use google:remoting namespace to export remoting specific error code. Jingle does not provide enough error codes for chromoting. So this change is to add an error-code tag under 'google:remoting' namespace in JingleMessage, and export chromoting specific error code under this node and namespace. BUG= 616156 Review-Url: https://codereview.chromium.org/2026123002 Cr-Commit-Position: refs/heads/master@{#398387} [modify] https://crrev.com/d1ee82f8fe9fd81b8ecb6b668f0acf0fbaa262c2/remoting/protocol/errors.cc [modify] https://crrev.com/d1ee82f8fe9fd81b8ecb6b668f0acf0fbaa262c2/remoting/protocol/errors.h [modify] https://crrev.com/d1ee82f8fe9fd81b8ecb6b668f0acf0fbaa262c2/remoting/protocol/jingle_messages.cc [modify] https://crrev.com/d1ee82f8fe9fd81b8ecb6b668f0acf0fbaa262c2/remoting/protocol/jingle_messages.h [modify] https://crrev.com/d1ee82f8fe9fd81b8ecb6b668f0acf0fbaa262c2/remoting/protocol/jingle_messages_unittest.cc [modify] https://crrev.com/d1ee82f8fe9fd81b8ecb6b668f0acf0fbaa262c2/remoting/protocol/jingle_session.cc [modify] https://crrev.com/d1ee82f8fe9fd81b8ecb6b668f0acf0fbaa262c2/remoting/protocol/name_value_map.h
,
Jun 7 2016
|
||
►
Sign in to add a comment |
||
Comment 1 by zijiehe@chromium.org
, May 31 2016