Hi guys, on holiday so brief reply! My workaround code does actually only rely
on the order in the URL itself, as it was solving that exact problem of
formValueKeys() not being in order. The explanation of why needed is a bit
involved. Thanks for the replies.
John
On 27 May 2014, at 05:00,
My workaround code does actually only rely on the order in the URL itself, as
it was solving that exact problem of formValueKeys() not being in order. The
explanation of why needed is a bit involved. Thanks for the replies.
John
On 27 May 2014, at 05:00, Aaron Rosenzweig wrote:
Hi Cristoph,
Hi Cristoph,
Order may be important to him if he has web server rewrite rules in place.
AARON ROSENZWEIG / Chat 'n Bike
e: aa...@chatnbike.com t: (301) 956-2319
On May 22, 2014, at 5:39 PM, CHRISTOPH WICK | i4innovation GmbH, Bonn
c...@i4innovation.de wrote:
Hi John,
Hi John,
If you read the documentation of WORequest's formValueKeys method, it says:
The returned array is not sorted in any particular order, and is not
necessarily sorted in the same order on successive invocations of this method.
Hi List,
I note that WORequest.formValues() jumbles up the order of the values from a
url. Is there a simple way to get them in order, or do I need to parse them out
myself? I understand that normally the order shouldn't be important, but I have
what I feel is a reasonable purpose for needing
My workaround to put them back in order, using a TreeMap to sort on the index
position within the URI.
NSArrayString formKeys = request().formValueKeys();
String uriStr = request().uri();
TreeMapInteger, String orderedKeysMap = new TreeMapInteger,
String();
?key2=val2array=1key=valarray=2array=3
On May 21, 2014, at 9:56 AM, John Pollard j...@pollardweb.com wrote:
My workaround to put them back in order, using a TreeMap to sort on the index
position within the URI.
NSArrayString formKeys = request().formValueKeys();
String
