Hi all,
This is a great use case that could be nicely solved by a combination of the TunnelService indeed, to define an encoding preference via a “min” extension, associated to an Encoding.JAVASCRIPT_MINIFICATION. This would update the Request#clientInfo#acceptedEncodings property. Then, the upcoming EncoderService could automatically wrap the response entity to minify if needed the JavaScript representations, using the EncoderFilter. To facilite the support of new encodings, we should support pluggable EncodingHelper that would allow new extensions to be discovered (YCompressor, JSMin, Zip, etc). I’ve added notes to this RFE: “Add EncoderService (similar to DecoderService)” http://restlet.tigris.org/issues/show_bug.cgi?id=208 Regarding caching, I think this should be treated as an orthogonal aspect across the board, based on response entities’ caching properties. The CachingService would have a pluggable storages, ideally the most requested entities should stay in memory while the less requested ones could land in a static directory, all configurable of course. “Add caching support” http://restlet.tigris.org/issues/show_bug.cgi?id=25 “Add caching support to Filter according to incoming Tag” http://restlet.tigris.org/issues/show_bug.cgi?id=772 All those features look really important to me at this point, so I’ve targeted them for 2.1 M1 and 2.1 M2. Best regards, Jerome -- Restlet ~ Founder and Technical Lead ~ <http://www.restlet.org/> http://www.restlet.org Noelios Technologies ~ <http://www.noelios.com/> http://www.noelios.com De : Thierry Boileau [mailto:thierry.boileau.noel...@gmail.com] Envoyé : vendredi 27 août 2010 16:21 À : discuss@restlet.tigris.org Objet : Re: Best way to get automatic JavaScript minification in Restlet Hello Tim, I'm sorry for my very late answer. You can also wrap the response's representation into a custom one that aims at applying the minification process. You can have a look at the Encoder filter, especially in the "encode" method which uses an EncodeRepresentation. Best regards, Thierry Boileau Perfect, thanks! --tim On Wed, Jul 28, 2010 at 7:43 PM, Tal Liron <tal.li...@threecrickets.com> wrote: I've handled it differently for Prudence: I create static unified/minifed files on-the-fly to be served via a Directory. If you request "all.min.js", all .js files in that directory are unified (in alphabetical order) and minifed. The filter can detect if any of the source files has been updated, and the interval between such tests can be configured. This seems to me the best way to go because the case for serving static files has already been optimized. (Other static web servers/CDNs can easily be used instead of Restlet's Directory.) See the code in JavaScriptUnifyMinifyFilter (LGPL): http://code.google.com/p/prudence/source/browse/#svn/trunk/java/com.threecrickets.prudence/src/com/threecrickets/prudence/util%3Fstate%3Dclosed There's also a similar class for CSS. (There might be an issue with method and concurrent file locking on certain operating systems -- haven't done a lot of testing yet, but I'm sure that case would be easy to fix.) -Tal On 07/28/2010 05:27 PM, Tim Peierls wrote: > I wrote a Restlet Filter to minify application/x-javascript resources > in afterHandle (using JSMin now, but I'll probably switch to YUI > Compressor). > > But is that all I can do with it? It feels as though this should be > plugged into the TunnelService, with ways to take requests for > foo.min.js, say, and return a minified foo.js, with caching and all > those goodies, yet still return plain, unminified foo.js when it's > requested. > > Feels like this must have been done already, but I can't find > anything. Pointers? Advice? > > --tim > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447 <http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2639913> &dsMessageId=2639913 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2653449
