[Pharo-project] Is serving files different in Pharo?
Mart-Mari Breedt wrote on Pharo list [1]
I got the answer to my problem here: http://bugs.squeak.org/view.php?id=7397
Why isnt the fix included into KomServer by default or the implementation in pharo changed by default? Pharo has: mimeType ^MIMEDocument guessTypeFromName: self name. The fix is mimeType ^MIMEDocument guessTypeFromName: self asUrl Should we or seaside dev care? Bye T. [1] http://lists.gforge.inria.fr/pipermail/pharo-project/2009-October/015314.htm... -- Neu: GMX DSL bis 50.000 kBit/s und 200,- Euro Startguthaben! http://portal.gmx.net/de/go/dsl02
Torsten Bergmann wrote:
Mart-Mari Breedt wrote on Pharo list [1]
I got the answer to my problem here: http://bugs.squeak.org/view.php?id=7397
Why isnt the fix included into KomServer by default or the implementation in pharo changed by default?
the implementation in Phao changed. asUrl shouldn't be used anymore. There are already one or two other places where seaside takes care of differences between Pharo and Squeak IIRC. But isn't Pharo now the default platform for seaside? Michael
Pharo has:
mimeType ^MIMEDocument guessTypeFromName: self name.
The fix is
mimeType ^MIMEDocument guessTypeFromName: self asUrl
Should we or seaside dev care?
Bye T.
[1] http://lists.gforge.inria.fr/pipermail/pharo-project/2009-October/015314.htm...
participants (2)
-
Michael Rueger -
Torsten Bergmann