"Diethelm Guallar, Gonzalo" wrote:
>
> Hello,
>
> I know Turbine tries to help the user/programmer by converting
> the form parameter names to a single case (I think it is lower).
> To me, this sounds suspiciously like dictating policy, and I have
> at least one example where doing this is not a good idea: I'm
> building a Turbine app that will interact with a legacy mainframe
> system via a message queuing component (think MQ). The parameter
> names in the mainframe system are fixed, and I can't change them;
> they seem to be (until now) all uppercase, so I have just been
> switching the names back to uppercase, but this is clearly a hack.
> If I find a mIxEd case parameter somewhere, I will have to
> maintain some kind of mapping between Turbine's idea of parameter
> names and the back-end's, and that would be a PITA.
>
> Here is my proposal: make this case squishing configurable:
>
> # I'm not sure about the parameter name or hierarchy...
> # Maybe "squishing" is not a very good name... How about
> # url.case.conversion?
> #
> # Possible values: none, upper, lower, capitalized
> # Default value: lower
> url.case.squishing=lower
+1, good that the default is the same as what Turbine currently does.
--
Daniel Rall <[EMAIL PROTECTED]>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
