Status: Accepted
Owner: [hidden email] Labels: Milestone-1.4 New issue 4469 by [hidden email]: Clean up old HTTP Code http://code.google.com/p/pharo/issues/detail?id=4469 -> rewrite users to use Zinc -> Remove old code _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Updates:
Labels: -Milestone-1.4 Comment #1 on issue 4469 by [hidden email]: Clean up old HTTP Code http://code.google.com/p/pharo/issues/detail?id=4469 (No comment was entered for this change.) _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Updates:
Labels: Type-Cleanup Comment #2 on issue 4469 by [hidden email]: Clean up old HTTP Code http://code.google.com/p/pharo/issues/detail?id=4469 (No comment was entered for this change.) _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #3 on issue 4469 by [hidden email]: Clean up old HTTP Code http://code.google.com/p/pharo/issues/detail?id=4469 hasn't this been almost completed? _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #4 on issue 4469 by [hidden email]: Clean up old HTTP Code http://code.google.com/p/pharo/issues/detail?id=4469 yes it is ;-) I just can't find the issue where it was done; it is the issue that we did together on the sprint _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #5 on issue 4469 by [hidden email]: Clean up old HTTP Code http://code.google.com/p/pharo/issues/detail?id=4469 Hmm... things left to do: => references to HttpSocket, HTTPProgress, HTTPClient => Deprecate the classes _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #6 on issue 4469 by [hidden email]: Clean up old HTTP Code http://code.google.com/p/pharo/issues/detail?id=4469 See http://code.google.com/p/pharo/issues/detail?id=6649 as yet another step to make this possible. _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #7 on issue 4469 by [hidden email]: Clean up old HTTP Code http://code.google.com/p/pharo/issues/detail?id=4469 Yet another step is http://code.google.com/p/pharo/issues/detail?id=6650 _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #8 on issue 4469 by [hidden email]: Clean up old HTTP Code http://code.google.com/p/pharo/issues/detail?id=4469 http://code.google.com/p/pharo/issues/detail?id=6741 Replace the whole HttpUrl downloading protocol _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #9 on issue 4469 by [hidden email]: Clean up old HTTP Code http://code.google.com/p/pharo/issues/detail?id=4469 http://code.google.com/p/pharo/issues/detail?id=6739 Remove URI client classes concept _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #10 on issue 4469 by [hidden email]: Clean up old HTTP Code http://code.google.com/p/pharo/issues/detail?id=4469 HTTPProgress can/must stay. http://code.google.com/p/pharo/issues/detail?id=6674 Make HTTPProgress a proper object _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #11 on issue 4469 by [hidden email]: Clean up old HTTP Code http://code.google.com/p/pharo/issues/detail?id=4469 http://code.google.com/p/pharo/issues/detail?id=6650 RBInternalSpellChecker not using 2.0 API _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #12 on issue 4469 by [hidden email]: Clean up old HTTP Code http://code.google.com/p/pharo/issues/detail?id=4469 OK, I think we are finally there in 20315: - there are no users of HTTPClient - there are no users of HTTPSocket (except for HTTPClient) - ZnHTTPSocketFacade is only needed for HTTPSocket These three classes (and their unit tests) can be either deprecated or removed. If we choose removal, I have to move ZnHTTPSocketFacade to pre-pharo-2 at the Zn level. Another option would be to remove HTTPClient and HTTPSocket, but keep the class methods on HTTPSocket that are delegated to ZnHTTPSocketFacade, and deprecate them. Any opinions ? _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #13 on issue 4469 by [hidden email]: Clean up old HTTP Code http://code.google.com/p/pharo/issues/detail?id=4469 http://code.google.com/p/pharo/issues/detail?id=6757 Nuke HTTPClient and HTTPSocket and deprecated ZnHTTPSocketFacade _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Updates:
Status: Closed Comment #14 on issue 4469 by [hidden email]: Clean up old HTTP Code http://code.google.com/p/pharo/issues/detail?id=4469 so this is done? _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #15 on issue 4469 by [hidden email]: Clean up old HTTP Code http://code.google.com/p/pharo/issues/detail?id=4469 I think this can be closed. All the old HTTP code is gone. There is only a small backwards API on ZnHTTP[SocketFacade] that is deprecated and that can be removed at any time. The URL/URI/ZnUrl problem is still present though. _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Free forum by Nabble | Edit this page |