Derrell Lipman wrote:
> 
> 
> 
> 'result' here is probably an array, which JavaScript considers to be an
> Object. There are two easy ways to look at the actual contents:
> 
>    1. qx.dev.Debug.debugObject() will recursively descend through any
> object
>    and display it. (You might also consider qx.dev.DebugObjectToString().)
>    2. Using Firebug, the fabulous Firefox debugger, select the "Net" tab,
>    and look at the actual result being sent back on the wire. With
> Firebug, you
>    can also set a breakpoint in your handler function, to look at the
> value of
>    'result'.
> 
> Cheers,
> 
> Derrell
> 
> 

Hi Darrell,

debugObjectToString() revealed the contents to be:

    Result of async call (debug): Array, length=5:
    ------------------------------------------------------------
    0: Object
      id: null
      requests: . $params[0] .
    1: Object
      id: null
      requests: . $params[0] .
    2: Object
      id: null
      requests: . $params[0] .
    3: Object
      id: null
      requests: Hello there
   4: Object
      id: null
      requests: Hello there you
    indexOf: function indexOf() { [native code] }
    lastIndexOf: function lastIndexOf() { [native code] }
    forEach: function forEach() { [native code] }
    filter: function filter() { [native code] }
    map: function map() { [native code] }
    some: function some() { [native code] }
    every: function every() { [native code] }
    ============================================================

So...should:
(1) my client iterate through the returned object to extract the contents
based on what I have learned from debugObjectToString(), or
(2) should the server process the array into something the client can work
with more easily?

Thanks,
Kim


--
View this message in context: 
http://qooxdoo.678.n2.nabble.com/preparing-data-for-rpc-transmission-from-php-to-qooxdoo-tp6839664p6842032.html
Sent from the qooxdoo mailing list archive at Nabble.com.

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to