> + this.readLen = this.metaData.getContentLength().intValue();
> +
> + this.nextPayload = getNextPayload();
> + }
> +
> + @Override
> + public boolean hasNext() {
> + return (nextPayload != null);
> + }
> +
> + @Override
> + public Payload next() {
> + Payload payload;
> +
> + payload = nextPayload;
> + nextPayload = getNextPayload();
> Do we need some kind of synchronization here, or will next() never be
> concurrently called from two separate threads?
Currently it's only
`org.jclouds.openstack.swift.blobstore.strategy.internal.SequentialMultipartUploadStrategy`
that makes use of this iterator, and based on it's usage, thread safety
doesn't seem to be an issue.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/192/files#r8112529
