Jan 15, 2010 at 3:23 AM
Edited Jan 15, 2010 at 3:25 AM
Thanks for the heads-up.
Actually I've run into a URI too large error in the generateText() & inlineCss() methods, but not elsewhere -- which is why I put the notes in the documentation that those methods should not use serial requests, but use xml-rpc.
In what method did you get the error?
Changing the request from a GET to a POST had no effect for me, because the URI length is the same regardless of GET/POST method and the MC server rejected it in both cases -- my request length was in the 40k+ range.
Thanks for bringing this up though, I had thought about changing the method at one time a while back & completely forgot about it. I prefer using POST anyway, it was just an oversight.
I am changing the method to POST for the 'final' v1.2.2 version -- it's a simple 1 line change in the apiHelper.SerialRequestResponse() method to add the line
wRequest.Method = "POST";
I can't think of a real good reason off-hand to not just change the method to a POST and not worry about a MethodType parameter, other than the always popular 'choice' reason.
Anybody else have any thoughts?
FYI: I'm delaying the final v1.2.2 version until Monday the 18th -- between some refactoring I'm doing on the Validator() & ValidateInput() classes & client work, I need the weekend to finish testing & tweaking.
I'll put a note up tomorrow with the schedule change & notes.