I think it's worthwhile to say how a feature benefits you for either: * How it fits into a real world application * How it makes development of said application (or in general) better/easier
My reason for this is that there are several peices of introspection that wouldn't be used for an app, but WOULD be used when there's something to debug. Getting a list of filters is an example of this. Rob Seeger Dossy Shiobara wrote on 2/7/2005, 4:13 PM: > I also want to remind folks that simply stating a desire for a feature > doesn't put much weight on it. Describing how the feature would fit > into a real application that you are either building and/or will build > gives it more weight. This prevents people from "asking for the moon" > and better serves those who are building products which rely on > AOLserver as an underlying technology in the stack. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
