Hi all, ok, suggestion: if we change Kom and Seaside to use the message contentType where they expect a mime type string, then it would be easy to make it work on both Pharo and Squeak without too much trouble. Seaside doesn't call mimeType on many places and usage is somewhat inconsistent right now as in httpResponse contentType = aHandler mimeType
Comments? Suggestions? Michael _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
