Re: callback success STATUS OK

2014-03-05 Thread Ally Ogilvie
JIRA Issue https://issues.apache.org/jira/browse/CB-6165


On Fri, Feb 28, 2014 at 12:19 AM, Andrew Grieve agri...@chromium.orgwrote:

 Sounds fine to me. Would be a bit strange if people were relying on that.


 On Thu, Feb 27, 2014 at 6:42 AM, Erik Jan de Wit ede...@redhat.com
 wrote:

  +1 for removing this
 
  This behaviour is also not the same on all platforms I've noticed that on
  iOS OK is passed, but not on android
 
  On 27 Feb,2014, at 8:35 , Ally Ogilvie aogil...@wizcorp.jp wrote:
 
   Since the very beginning a success callback without message (native
  args)
   has returned the string OK to the success function in JavaScript.
  
   I think there is no reason for this to be. I think the reason it's
 there
  is
   because it's been there from the beginning. But we should get rid of
 this
   now.
  
   Looking for some agreement (+1) on this before chalking it up on the
 todo
   list.
  
   Thanks.
  
   Ally.
 
 




-- 
http://www.wizcorp.jp/Ally Ogilvie
Lead Developer - MobDev. | Wizcorp Inc. http://www.wizcorp.jp/
--
TECH . GAMING . OPEN-SOURCE WIZARDS+ 81 (0)3-4550-1448 |
Websitehttp://www.wizcorp.jp/
 | Twitter https://twitter.com/Wizcorp |
Facebookhttp://www.facebook.com/Wizcorp
 | LinkedIn http://www.linkedin.com/company/wizcorp


Re: callback success STATUS OK

2014-02-27 Thread Erik Jan de Wit
+1 for removing this

This behaviour is also not the same on all platforms I’ve noticed that on iOS 
“OK” is passed, but not on android 

On 27 Feb,2014, at 8:35 , Ally Ogilvie aogil...@wizcorp.jp wrote:

 Since the very beginning a success callback without message (native args)
 has returned the string OK to the success function in JavaScript.
 
 I think there is no reason for this to be. I think the reason it's there is
 because it's been there from the beginning. But we should get rid of this
 now.
 
 Looking for some agreement (+1) on this before chalking it up on the todo
 list.
 
 Thanks.
 
 Ally.



Re: callback success STATUS OK

2014-02-27 Thread Andrew Grieve
Sounds fine to me. Would be a bit strange if people were relying on that.


On Thu, Feb 27, 2014 at 6:42 AM, Erik Jan de Wit ede...@redhat.com wrote:

 +1 for removing this

 This behaviour is also not the same on all platforms I’ve noticed that on
 iOS “OK” is passed, but not on android

 On 27 Feb,2014, at 8:35 , Ally Ogilvie aogil...@wizcorp.jp wrote:

  Since the very beginning a success callback without message (native
 args)
  has returned the string OK to the success function in JavaScript.
 
  I think there is no reason for this to be. I think the reason it's there
 is
  because it's been there from the beginning. But we should get rid of this
  now.
 
  Looking for some agreement (+1) on this before chalking it up on the todo
  list.
 
  Thanks.
 
  Ally.




callback success STATUS OK

2014-02-26 Thread Ally Ogilvie
Since the very beginning a success callback without message (native args)
has returned the string OK to the success function in JavaScript.

I think there is no reason for this to be. I think the reason it's there is
because it's been there from the beginning. But we should get rid of this
now.

Looking for some agreement (+1) on this before chalking it up on the todo
list.

Thanks.

Ally.