I know *nothing* about Zinc, but my first thought is weak collections and how they are not thread safe (which they need to be) and are not self-repairing after finalization - they end up w/ retained nils. Dolphin blazed the correct trail on this in the mid to late 90s. ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Sean P. DeNigris [sean@clipperadams.com] Sent: Tuesday, June 26, 2012 11:33 PM To: pharo-project@lists.gforge.inria.fr Subject: [Pharo-project] Zinc intermittently returning nil The following all intermittently return nil. When I do the same thing in Safari, I always seem to get the correct answer (plain text). (ZnEasy get: 'https://ci.lille.inria.fr/pharo/job/Pharo-2.0/lastSuccessfulBuild/api/xml?xp...') contents. (ZnClient new get: 'https://ci.lille.inria.fr/pharo/job/Pharo-2.0/lastSuccessfulBuild/api/xml?xp...') contents. (ZnUrl fromString: 'https://ci.lille.inria.fr/pharo/job/Pharo-2.0/lastSuccessfulBuild/api/xml?xp...') retrieveContents. Even this returns nil intermittently (maybe less frequently, not sure): client := ZnClient new. client systemPolicy; url: 'https://ci.lille.inria.fr/pharo/job/Pharo-2.0/lastSuccessfulBuild/api/xml?xp...'; accept: ZnMimeType textPlain. client get contents. Sean -- View this message in context: http://forum.world.st/Zinc-intermittently-returning-nil-tp4636820.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.