Issue 6687 in pharo: Zinc-HTTP Enh

Status: FixToInclude
Owner: [hidden email]
CC: [hidden email]
Labels: Type-Bug Milestone-2.0

New issue 6687 by [hidden email]: Zinc-HTTP Enh
http://code.google.com/p/pharo/issues/detail?id=6687

Well, no ;-) I think it would be better to only do a retry on NetworkErrors  
and ZnParseErrors.
On the other hand, the ifFail functionality should trigger on any Error.  
We'll see.
Thanks again for the help, you made Pharo faster by removing my explicit  
Delays ;-)

Sven

Sven Van Caekenberghe uploaded a new version of Zinc-HTTP to project Zinc  
HTTP Components:
http://www.squeaksource.com/ZincHTTPComponents/Zinc-HTTP-SvenVanCaekenberghe.301.mcz

==================== Summary ====================

Name: Zinc-HTTP-SvenVanCaekenberghe.301
Author: SvenVanCaekenberghe
Time: 17 September 2012, 10:10:49 am
UUID: 85632c09-a6c4-40e9-b29b-1c5e86d07ead
Ancestors: Zinc-HTTP-SvenVanCaekenberghe.300

Fixed a bug where HTTPProgress notifications would trigger a retry.
Thanks Camillo Bruni for finding this problem and suggesting a solution.
Now, retries are only triggered by (NetworkError, ZnParseError), while the  
#ifFailBlock will be trigger on any Error.
Furthermore, #noteRetrying: and noteIgnoringExceptionOnReusedConnection:  
will report on the actual exception.
The default #ifFailBlock is now [ :exception | exception pass ] for some  
cleaner code.

--


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #1 on issue 6687 by [hidden email]: Zinc-HTTP Enh
http://code.google.com/p/pharo/issues/detail?id=6687

everything would be easier if this would be commited to the inbox.



_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: WorkNeeded

Comment #2 on issue 6687 by [hidden email]: Zinc-HTTP Enh
http://code.google.com/p/pharo/issues/detail?id=6687

When I merge this I get 5 conflicts


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #3 on issue 6687 by [hidden email]: Zinc-HTTP Enh
http://code.google.com/p/pharo/issues/detail?id=6687

I don't think that Zinc is ready right now for integration, I have to  
recheck everything against the latest fresh image.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Closed

Comment #4 on issue 6687 by [hidden email]: Zinc-HTTP Enh
http://code.google.com/p/pharo/issues/detail?id=6687

So I close it for now.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker