Keith Hodges wrote:
The ultimate aim here, is to be able to hand a rio as a parameter into a tool, and that tool should be able to read and write to the file represented by the rio, irrespective of whether that rio represents a remote file, a gziped file or a file within a zip file. Its basically polymorphism in action, and I would like to think that that is good design.
Unfortunately that is going to come back and bite you big time in an real application as we learned in Sophie. You need to know that you are working with an archive or remote server, as there specific conditions and failures that can't be hidden. For instance you don't want to recompress images etc when storing files in an archive. And working with a remote directory is so frigging complicated in real life that you hardly ever want to do that.
Michael _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
