|
On Wed, Aug 1, 2012 at 4:51 PM, Mariano Martinez Peck <[hidden email]> wrote:
On Wed, Jul 25, 2012 at 11:46 AM, Sven Van Caekenberghe <[hidden email]> wrote:
Hi Mariano,
(I can't access the file you gave as an example, probably an extra #username:password: is needed)
You are making it more difficult than it has to be: this gives you the bytes you want
ZnClient new
get: 'http://zn.stfx.eu/zn/string.fuel'.
With some better system parameters this becomes
ZnClient new
systemPolicy;
beOneShot;
accept: ZnMimeType applicationOctetStream;
url: 'http://zn.stfx.eu/zn/string.fuel';
get.
But what you really want is something like:
ZnClient new
systemPolicy;
beOneShot;
accept: ZnMimeType applicationOctetStream;
url: 'http://zn.stfx.eu/zn/string.fuel';
contentReader: [ :entity | FLMaterializer materializeFromByteArray: entity contents ];
get.
You can experiment with #streaming: true but that is only worth it for large (MB) files. IMHO.
Hi Sven. Indeed, this last piece of code was what I was searching for. However, my "experiment" was to be able to directly revive test failures form Jenkins.
But it turns out that it is not possible to have each .fuel separated...instead we have one big zip for all of them. So at the end what Sean did is to have a zip with all .fuel files and the image itself. And he even wrote a UI for that. So my experiment ended there regarding Zinc.
anyway, at least I learnt how to do it. thanks Sven!
-- Mariano http://marianopeck.wordpress.com
-- Mariano http://marianopeck.wordpress.com
|