Doh! You're so right Peter...
I'm blindly thinking of the entire transaction in JSON. You're talking
about a protocol change for serialization of just one var in there.
However, (as far as CF8 is concerned) Alan's suggestion of
Duplicate(session) worked. The type mismatch error is gone and a struct
has passed through with nary a grunt. Now to try this on the other CFML
platforms...
Al
On 8/22/2011 4:41 PM, Peter J. Farrell wrote:
Alan Holden said the following on 08/22/2011 06:27 PM:
But this is part of some established dialog between servers, and I
don't have much leeway in this part of the design. I wanted to
suggest passing the entire session (so we don't have to maintain
every fickle change within it), but thought it wise to actually try
it first.
Even if it's SOAP, you can pass a JSON string in the SOAP request to
simplify things. SOAP is awful as it's a "strictly" typed interface
where the world of HTTP is not (and even communicating with SOAP
between two strictly typed languages is a pain -- there is no mapping
between datatype A in language X and datatype A in language Y -- it a
kludge).
--
official tag/function reference: http://openbd.org/manual/
mailing list - http://groups.google.com/group/openbd?hl=en
