Well, I'm not sure what you did. And this MIME support is mainly used for a server rather than a client. So your client must know how to deal with the given MIME. I think your client is not going to use my mime.scm, unless you're writing a web browser. If you do, you must have many handlers for these mime types and decide which to go with the information "mime.scm" gives you. But in general, you don't have to use mime.scm in your client/browser, the server will return mime type to you. And I think "http-get" could get whatever data from remote, so if you're not writing a web browser, you just store the data to a file or redirect to player something. In this case, you don't have to detect mime type automatically. Anyway, thanks for reply. ;-) On Thu, Feb 23, 2012 at 11:03 PM, Catonano wrote: > > > Il giorno 23 febbraio 2012 15:53, Nala Ginrut ha > scritto: > > There's no mime support in Guile module, so I modified the mime code of my >> project Ragnarok and format a patch. >> It's easy to use: >> (use-modules (web mime)) >> (define mime (make )) >> (mime:guess mime 'pdf) >> ==> application/pdf >> (mime:guess mime 'php) >> ==> application/x-httpd-php >> >> Maybe useful for some guys~ >> Any comments? >> > > just recently I happened to download something and the mimetype was not > textual even though the content was textual indeed (it was a .ram link hat > is a url starting with rtsp://...) > > So what I got back was a bytevector and I had to decode it in my code; a > ugly hack > > Personally I'd be interested in see how your stuff could be used together > with http-get to download something with a weird mimetype > > Thanks >