blob: ff4420a3b42abc74a0f8dd913bd59651cbde30bf [file] [log] [blame]
<?xml version="1.0"?>
<!--
/*
* Copyright 2001-2004 The Apache Software Foundation.
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
-->
<document>
<properties>
<title>Application Service Proposal</title>
</properties>
<body>
<section name="Parameter parser and its ilk">
<ul>
<li>
clean up and orthogonalize APIs (add vs append vs set)
</li>
<li>
what the heck is uploadData? I think UploadService/FileItems do the
trick just fine
</li>
<li>
BaseValueParser should not extend RecyclableSupport. If I understand
the pattern correctly, it should include an instance of
RecyclableSupport and delegate Recyclable interface method to it.
The same goes for TurbineDefaultRunData. To prevent people from doing
that RecyclableSupport should not implement Recyclable itself. AFAIK, this
kind of apprach is used to emulate multiple inheritance in Java.
I'd appreciate a comment on this issue from Ilkka.
</li>
</ul>
</section>
</body>
</document>