In GLASS, I have arranged to prompt for new/missing credentials when the save fails due to an HTTP error ... It's a bit of a hack, since the HTTP client doesn't throw an error, but it is better than the alternative ... only experts know how to fix the credentials using the debugger:) In my case I wanted to minimize changes to the HTTP client, but I would think that for Pharo, explicit error handling would be an improvement for the HTTP client anyway... Dale Stéphane Ducasse wrote:
before reverting it could we not have another solution ;) Because indeed I never went inside the debugger to catch the credentials Stef
On Jun 15, 2010, at 9:25 AM, Hernán Morales Durand wrote:
2010/6/15 Lukas Renggli <renggli@gmail.com>:
This is because "2" should not be created. If a copy cannot be saved then there is no reason to increment the version number with the failed attempt. May deserve another issue entry?
Please comment I would like to read opinions on this. I noticed this problem too. The previous behavior was better, at least if you knew how to fix you credentials in the debugger.
Ok then revert the change if you like, although the Debugger is probably the most powerful tool we have I see it as a tool for editing code, not configurations (I've never heard of anyone going though Debugger to set credentials in MC) and newbies may perceive a problem with MC instead of their settings or network problems.
Hernán
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project