flex-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeffry Houser <jef...@dot-com-it.com>
Subject Re: Can I control the parameter order in an HTTPService Post?
Date Wed, 12 Jul 2017 13:36:34 GMT
  Not doing a get, doing a post, FWIW.


On 7/11/2017 5:05 PM, Alex Harui wrote:
> I don't know this code at all, so I could be missing something, but I saw
> this in AbstractOperation's sendBody:
>
> if (filter != null)
>          {
>              // TODO: does this need to run on the array version of the
> parameters
>              ctype = filter.getRequestContentType(this, parameters, ctype);
>              urlToUse = filter.serializeURL(this, parameters, urlToUse);
>              parameters = filter.serializeBody(this, parameters);
>          }
>
> If you are doing a GET, I think you could use serializeURL to put the
> parameters on the urlToUse in the order you want.  If the default
> serializeURL doesn't do what you want, you would subclass it and override
> serializeURL.
>
>
> Of course, at that point, it might be easier to use URLLoader ;-)
>
> -Alex
>
>
> On 7/11/17, 1:15 PM, "Jeffry Houser" <jeffry@dot-com-it.com> wrote:
>
>>   I looked into a Serialization Filter too.  Explicitly, the
>> serializeParameters() function.  Unfortunately, it returns a generic
>> object and is called before the parameters are processed in the
>> sendBody() function; meaning it had no affect.
>>
>>
>> On 7/11/2017 2:13 PM, Alex Harui wrote:
>>> Ah yes.  It looks like the parameters might become the body.  It appears
>>> there is a class called a SerializationFilter that might help you
>>> translate the parameters to the right parts of the request.
>>>
>>>   From AbstractOperation:
>>>
>>> if (filter != null)
>>>           {
>>>               // TODO: does this need to run on the array version of the
>>> parameters
>>>               ctype = filter.getRequestContentType(this, parameters,
>>> ctype);
>>>               urlToUse = filter.serializeURL(this, parameters, urlToUse);
>>>               parameters = filter.serializeBody(this, parameters);
>>>           }
>>>
>>>
>>>
>>> HTH,
>>> -Alex
>>>
>>> On 7/11/17, 11:03 AM, "Jeffry Houser" <jeffry@dot-com-it.com> wrote:
>>>
>>>> On 7/11/2017 12:32 PM, Alex Harui wrote:
>>>>> But interestingly, the code also looks like you can give
>>>>> HTTPService.send() the request string instead of an object of
>>>>> name/value
>>>>> pairs and it will use the string.
>>>> The code does look like that, and it was the first thing I tried. The
>>>> string does not get added to the outgoing request; it just kind of
>>>> vanishes.
>>>>
>>>>
>>>> -- 
>>>> Jeffry Houser
>>>> Technical Entrepreneur
>>>>
>>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.dot-
>>>> co
>>>>
>>>> m-it.com&data=02%7C01%7C%7C9fdb398e607e41d6fb8708d4c8872791%7Cfa7b1b5a7b
>>>> 34
>>>>
>>>> 438794aed2c178decee1%7C0%7C0%7C636353930201694821&sdata=4yHa0MXp0JwJ7fjY
>>>> 3Z
>>>> gTz1kp5V9QO6T%2FooHdUFiIDHc%3D&reserved=0
>>>>
>>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.jeff
>>>> ry
>>>>
>>>> houser.com&data=02%7C01%7C%7C9fdb398e607e41d6fb8708d4c8872791%7Cfa7b1b5a
>>>> 7b
>>>>
>>>> 34438794aed2c178decee1%7C0%7C0%7C636353930201704830&sdata=%2B9xHHB0xsmt8
>>>> m7
>>>> a92lJyFX9%2FDJQYEbYSUyQIIHRl030%3D&reserved=0
>>>> 203-379-0773
>>>>
>> -- 
>> Jeffry Houser
>> Technical Entrepreneur
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.dot-co
>> m-it.com&data=02%7C01%7C%7Ce0b51fcdffd245b92a5f08d4c89fa97e%7Cfa7b1b5a7b34
>> 438794aed2c178decee1%7C0%7C0%7C636354035468010487&sdata=ee0SL0eI4x3XAHwCes
>> o2KB70P1fskNgc5Gj8Tunl6kg%3D&reserved=0
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.jeffry
>> houser.com&data=02%7C01%7C%7Ce0b51fcdffd245b92a5f08d4c89fa97e%7Cfa7b1b5a7b
>> 34438794aed2c178decee1%7C0%7C0%7C636354035468010487&sdata=rYiyQHpgw2pNr3X0
>> fr%2BiHE%2BuTEzh0fIF7iNCosT7Kp8%3D&reserved=0
>> 203-379-0773
>>

-- 
Jeffry Houser
Technical Entrepreneur
http://www.jeffryhouser.com
203-379-0773


Mime
View raw message