I want to repeat a question I earlier sent:
So what is the use case for the getters? Any examples? Because whoever is
in charge of constructing of the PushBuilder has already determined and
intended what is being pushed. I don't see why a builder needs to be
queried for what's just been set.
Also, after push(), it is documented that certain values will be cleared --
like path, etag, and lastModified. So I have some questions for the EG to
ponder:
1) Should there be a boolean that represents if the builder is "clean" for
a new build? A push would clean the builder.
2) Being reusable, should there be a count of how many pushes a builder
performs?
PS: You can eliminate the "abstract" keywords from all the methods.
Cheers,
Paul
On Sat, Nov 21, 2015 at 4:06 PM, Greg Wilkins <gregw_at_webtide.com> wrote:
>
> On 22 November 2015 at 02:55, Paul Benedict <pbenedict_at_apache.org> wrote:
>
>> Also will the builder methods throw ISE once the push() occurs?
>
>
> No. The intention is to allow several similar resources to be pushed, so
> the builder is able to be reused with just perhaps the path being changed.
>
>
>
>
> --
> Greg Wilkins <gregw@webtide.com> CTO http://webtide.com
>