Re: unified doXXX()

2010-03-04 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aryeh, On 3/2/2010 7:12 PM, Aryeh M. Friedman wrote: Christopher Schultz wrote: If that string above is your entire POST request body, then it's not properly formatted. Instead, it should be: call=8347812459870132405987234985023450987 or

Re: unified doXXX()

2010-03-02 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aryeh, On 3/2/2010 1:51 AM, Aryeh M. Friedman wrote: Yes we are and thats why I probably mistook the effect of it doing that as a side effect instead of a designed in feature... now that being said we have used that content day since the first few

Re: unified doXXX()

2010-03-02 Thread Aryeh M. Friedman
Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aryeh, On 3/2/2010 1:51 AM, Aryeh M. Friedman wrote: Yes we are and thats why I probably mistook the effect of it doing that as a side effect instead of a designed in feature... now that being said we have used that

Re: unified doXXX()

2010-03-02 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aryeh, On 3/2/2010 2:20 PM, Aryeh M. Friedman wrote: It gets null's on POST's only but only from the new input format (there are parts of the app that still use the old format and they work fine) Is this a new client, or just a new data format?

Re: unified doXXX()

2010-03-02 Thread Aryeh M. Friedman
Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aryeh, On 3/2/2010 2:20 PM, Aryeh M. Friedman wrote: It gets null's on POST's only but only from the new input format (there are parts of the app that still use the old format and they work fine) Is this a new

Re: unified doXXX()

2010-03-02 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aryeh, On 3/2/2010 3:48 PM, Aryeh M. Friedman wrote: Christopher Schultz wrote: Is this a new client, or just a new data format? Mark's suggestion that you may be using POST without the proper Content-Type would result in getting null for this

Re: unified doXXX()

2010-03-02 Thread Aryeh M. Friedman
Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aryeh, On 3/2/2010 3:48 PM, Aryeh M. Friedman wrote: Christopher Schultz wrote: Is this a new client, or just a new data format? Mark's suggestion that you may be using POST without the proper Content-Type

Re: unified doXXX()

2010-03-02 Thread Aryeh M. Friedman
Aryeh M. Friedman wrote: Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aryeh, On 3/2/2010 3:48 PM, Aryeh M. Friedman wrote: Christopher Schultz wrote: Is this a new client, or just a new data format? Mark's suggestion that you may be using POST without the

Re: unified doXXX()

2010-03-02 Thread Aryeh M. Friedman
Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aryeh, On 3/2/2010 3:48 PM, Aryeh M. Friedman wrote: Christopher Schultz wrote: Is this a new client, or just a new data format? Mark's suggestion that you may be using POST without the proper Content-Type

Re: unified doXXX()

2010-03-02 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aryeh, On 3/2/2010 4:05 PM, Aryeh M. Friedman wrote: Aryeh M. Friedman wrote: Aryeh M. Friedman wrote: Christopher Schultz wrote: I know this sounds silly, but we're getting down to the grasping-at-straws level, here, so bear with me: have you

Re: unified doXXX()

2010-03-02 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aryeh, On 3/2/2010 4:12 PM, Aryeh M. Friedman wrote: Also forgot to mention I already refactored the servlet to use pure hex encoding (namely we convert the entire request into a hex string so for example a old format message of

Re: unified doXXX()

2010-03-02 Thread Pid
On 02/03/2010 21:04, Aryeh M. Friedman wrote: Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aryeh, On 3/2/2010 3:48 PM, Aryeh M. Friedman wrote: Christopher Schultz wrote: Is this a new client, or just a new data format? Mark's suggestion that you may be using

Re: unified doXXX()

2010-03-02 Thread Aryeh M. Friedman
Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aryeh, On 3/2/2010 4:05 PM, Aryeh M. Friedman wrote: Aryeh M. Friedman wrote: Aryeh M. Friedman wrote: Christopher Schultz wrote: I know this sounds silly, but we're getting down to the

Re: unified doXXX()

2010-03-02 Thread Aryeh M. Friedman
Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aryeh, On 3/2/2010 4:12 PM, Aryeh M. Friedman wrote: Also forgot to mention I already refactored the servlet to use pure hex encoding (namely we convert the entire request into a hex string so for example a old format

Re: unified doXXX()

2010-03-01 Thread Aryeh M. Friedman
Pid wrote: On 28/02/2010 02:00, Aryeh M. Friedman wrote: I am refactoring a servlet we have used successfully for several years now to accommodate input that does not amen itself to HttpServletRequest.getParameter()... The only way it seems to be to handle our particular input (the

Re: unified doXXX()

2010-03-01 Thread Mark Thomas
On 01/03/2010 08:01, Aryeh M. Friedman wrote: Pid wrote: I want to preserve the single handler design but since getParameter barfs on our new input format and there is no unified raw input reader the only thing I can think of is make it so doGet and doPost use request.getQueryString() and

Re: unified doXXX()

2010-03-01 Thread Aryeh M. Friedman
Mark Thomas wrote: On 01/03/2010 08:01, Aryeh M. Friedman wrote: Pid wrote: I want to preserve the single handler design but since getParameter barfs on our new input format and there is no unified raw input reader the only thing I can think of is make it so doGet and doPost use

Re: unified doXXX()

2010-02-28 Thread Pid
On 28/02/2010 02:00, Aryeh M. Friedman wrote: I am refactoring a servlet we have used successfully for several years now to accommodate input that does not amen itself to HttpServletRequest.getParameter()... The only way it seems to be to handle our particular input (the nature/format of the

unified doXXX()

2010-02-27 Thread Aryeh M. Friedman
I am refactoring a servlet we have used successfully for several years now to accommodate input that does not amen itself to HttpServletRequest.getParameter()... The only way it seems to be to handle our particular input (the nature/format of the input is covered by an NDA so I can not