> Let's assume that mozilla uses "application/octet-stream" for any file it
> doesn't understand. That's the default type. I'm saying that treating a file
> (or any object) as "application/octet-stream" is different from knowing the
> file is "application/octet-stream" and mozilla should keep these cases
> distinct.
"application/octet-stream" is _defined_ as the "I don't really know what his
is, but it's not text" type in the MIME specs.
> I only took a quick look at these files so I'm probably missing something but
> I found the nsFSMultipartFormData class in nsFormSubmission.cpp which talks
> about multiplexing string and file streams. Although this class doesn't do
> what you need it does suggest that the necessary technique is known and should
> be easily adapted. Or I'm just wrong.
Please suggest how that should happen. I spent some time looking at it when
you first suggested this approach, and I see no simple (patching only one spot,
diff smaller than 100 lines or so) ways to do it.
Boris
--
It is forbidden to kill; therefore all murderers are punished
unless they kill in large numbers and to the sound of trumpets.
-- Voltaire
