on 6/14/01 10:02 AM, "Darren Gilroy" <[EMAIL PROTECTED]> wrote:
> Few, however, let the developer control something as fine-grained as
> normalizing the case of your form or url variables. There are lots of little
> things in Turbine that fit this pattern; it shows a care that many
> commercial applications lack.
Wow! Thanks...
Just for a bit of a history lesson, I added the "feature" of forcing the key
variables to lowercase in the ParameterParser when they went in because I
have developed so many applications where I would spend hours trying to
figure out why I wasn't getting my form data, only to realize that it was a
I instead of an l (ell) or something like that.
Eventually, someone came along and actually wanted control over that so they
added a feature to ParameterParser and the property to the TR.props file...
Even later on, someone figured to make PP an interface, instead of a class.
So, you can even write your own way of handling things. That is probably the
coolest solution. :-)
As you dig through Turbine's code, you will see this pattern all over the
place...if there is something you don't like, generally, you can easily
replace it with something else that you do like.
You are right, a lot of commercial solutions...and even OSS solutions don't
give you this level of control over the framework that Turbine does.
Hopefully, more people will realize that and either start to use Turbine or
modify their frameworks to copy us. :-)
-jon
--
"Open source is not available to commercial companies."
-Steve Ballmer, CEO Microsoft
<http://www.suntimes.com/output/tech/cst-fin-micro01.html>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
