I have noticed a couple of places where New and Old are used to identify improved and out-dated methodologies.

NewThreadedAppServer, serverSideInfoForRequestNew and filenamesForBaseNameNew

Is the plan to remove (at least the New*) names prior to the next release? If not, I would encourage it. Because if NewFunction starts getting used in production and needs to be supported, then at some point it fails to be New and you want to come up with another one.

I think it would be a good idea to say that using New* (where New indicates a new/experimental methodology) should be "unsupported" in the sense that once the New approach has been adopted, the name will be changed back to the standard name.
Thoughts?

-Stuart-





-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-devel

Reply via email to