>>> Saumont Pierre-Yves <[EMAIL PROTECTED]> 20-Mar-01 9:07:04 AM >>>
>In my opinion, doing so would lead to troubles : poor
>audio quality (due to MuLaw encoding), wasted bandwidth
>(while lossy, MuLaw encoding is not a very compressed format),
>heavy load on the server (MP3 decodig seems to be resource
>consumming). The only advantage would be saving space for
>storage.
I don't know anything about this. I thought you said that MuLaw was
the format that had to be used to actually play in a browser.
The idea of decoding an MP3 file on the server and downloading the
decoded stream isn't so mad.
First, servers have more processing power than clients (you were
suggesting I think that decoding in an Applet would be very slow - I
presume because of the speed of the client).
Second, if the MuLaw format is bulky the applet and servlet could
co-operate to reduce the bulk by transmitting in gzip.
Instead of sending to an applet one could send a raw audio file to
the browser.
Since the browser generally supplies enough information over the HTTP
connection to establish what operating system the client is running
the server could decode an MP3 file to one of a number of audio
formats depending on the OS used.
eg: send a wav file to ms-explorer clients, an au file to Mac
clients, etc...
It probably would work quite well... though I shouldn't think the
other people on the network where you were doing it would be very
pleased.
Nic
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
