chicken-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-users] ANN: scheme-complete.el 0.3


From: Ivan Shmakov
Subject: Re: [Chicken-users] ANN: scheme-complete.el 0.3
Date: Sat, 17 Nov 2007 12:04:54 -0000
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4

>>>>> "AS" == Alex Shinn <address@hidden> writes:

 > On Nov 14, 2007 4:05 PM, Ivan Shmakov <address@hidden> wrote:

 >>  Could the server be configured to send

 >> Content-Type: application/emacs-lisp
 >> Content-Transfer-Encoding: gzip

        s/Transfer-/, of course.

 >> instead of

 >> Content-Type: application/x-gzip

 >> so that browsers will allow to see the referenced file contents
 >> without saving?

 > I may be mistaken, but isn't that for the case when the server
 > compresses the .el file on the fly?

        The specification explicitly allows both uses:

--cut: RFC 2616--
14.11 Content-Encoding

   The Content-Encoding entity-header field is used as a modifier to the
   media-type. When present, its value indicates what additional content
   codings have been applied to the entity-body, and thus what decoding
   mechanisms must be applied in order to obtain the media-type
   referenced by the Content-Type header field. Content-Encoding is
   primarily used to allow a document to be compressed without losing
   the identity of its underlying media type.

       Content-Encoding  = "Content-Encoding" ":" 1#content-coding

   Content codings are defined in section 3.5. An example of its use is

       Content-Encoding: gzip

   The content-coding is a characteristic of the entity identified by
   the Request-URI. Typically, the entity-body is stored with this
   encoding and is only decoded before rendering or analogous usage.
--cut: RFC 2616--

        NB: the last sentence.

--cut: RFC 2616--
   However, a non-transparent proxy MAY modify the content-coding if the
   new coding is known to be acceptable to the recipient, unless the
   "no-transform" cache-control directive is present in the message.
--cut: RFC 2616--

        So, it doesn't matter /who/ have compressed the file, it matters
        that it /is/ compressed.

 > If you do that for a file named .el.gz, then wouldn't the browser
 > save the decompressed data still under the name .el.gz?

        That will depend on a browser.  Indeed, some browsers do it this
        way, and some don't.  Personally, I'd use `wget'.

 > The server doesnt yet support automatic compression, though I've been
 > meaning to rewrite it for ages now.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]