Received: by 10.180.105.38 with SMTP id gj6mr2421068wib.0.1342723680807;
        Thu, 19 Jul 2012 11:48:00 -0700 (PDT)
X-BeenThere: play-framework@googlegroups.com
Received: by 10.216.212.2 with SMTP id x2ls1499400weo.2.gmail; Thu, 19 Jul
 2012 11:47:48 -0700 (PDT)
Received: by 10.180.73.146 with SMTP id l18mr1384226wiv.4.1342723668588;
        Thu, 19 Jul 2012 11:47:48 -0700 (PDT)
Received: by 10.180.73.146 with SMTP id l18mr1384224wiv.4.1342723668574;
        Thu, 19 Jul 2012 11:47:48 -0700 (PDT)
Return-Path: <guillaume.b...@gmail.com>
Received: from mail-we0-f171.google.com (mail-we0-f171.google.com [74.125.82.171])
        by gmr-mx.google.com with ESMTPS id fb20si4698390wid.3.2012.07.19.11.47.48
        (version=TLSv1/SSLv3 cipher=OTHER);
        Thu, 19 Jul 2012 11:47:48 -0700 (PDT)
Received-SPF: pass (google.com: domain of guillaume.b...@gmail.com designates 74.125.82.171 as permitted sender) client-ip=74.125.82.171;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of guillaume.b...@gmail.com designates 74.125.82.171 as permitted sender) smtp.mail=guillaume.b...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-we0-f171.google.com with SMTP id x43so2591614wey.30
        for <play-framework@googlegroups.com>; Thu, 19 Jul 2012 11:47:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        bh=q4SPMqDUibk27sW9pHUKBqVgx4gsI/4LcQ18kdED3V0=;
        b=mKcApVCsCW5LIsMmeNnIRTkCpdTDwyymMprYwXLniVb5zAbeAFp7K10bNMalC3WY4Y
         MxOqb7kGPA2pPbBCPqV/tq6VvQp79zXOYpi9Nk2W1ESQxvYK1D2EMektASQ+aKuitJ5o
         AhXTTqGZbqXVZffZMrlV5yMW1a+hAgxcYGjhwWGRk/aer25SowAd22XCd55hf4+sZJL3
         piUy0+nlH/8Ae+mggI/QpN5zOSLmVkkHtCq4iIxJINUk7kaFbmXg5ihVw/gB4WXooC9t
         1ke9mcJNOrTEE0hH1v6H2rzqjytAoaSUsUuyxFTCFHSbX/OpLelBrK6Uv7NvNpzmgNTC
         wDYg==
Received: by 10.216.49.6 with SMTP id w6mr1820374web.207.1342723666758; Thu,
 19 Jul 2012 11:47:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.14.101.2 with HTTP; Thu, 19 Jul 2012 11:47:26 -0700 (PDT)
In-Reply-To: <CAPvS8WbqkkkjUVK2qb8HdbDY3EfKBBMVL=034b8+Dvzjsz0...@mail.gmail.com>
References: <CAC0Wrux+-DiHdqcX-H9w9omfnh0JAC0zViVYqR30MivQrBD...@mail.gmail.com>
 <CAPvS8WbqkkkjUVK2qb8HdbDY3EfKBBMVL=034b8+Dvzjsz0...@mail.gmail.com>
From: Guillaume Bort <guillaume.b...@gmail.com>
Date: Thu, 19 Jul 2012 11:47:26 -0700
Message-ID: <CAC0Wruz4ORo9G3YGmy3LzV3MUwth382mABk-Sbs+TqGRHyN...@mail.gmail.com>
Subject: Re: [play-framework] [2.x] Static assets handling performance
To: play-framework@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1

> I look forward to a day when a standardized cross-platform  solution is
> widely implemented.

This feature (WatchEvents) is available in NIO2 in Java 7. But for now
we will stick with JNotify for compatibility reasons.

On Thu, Jul 19, 2012 at 11:39 AM, C. Mundi <cmu...@gmail.com> wrote:
> I look forward to using the new capability, because I like the idea of
> serving static assets without a separate dedicated server.   Even if the new
> code works great for everyone today, some strategic caution may be a good
> idea.
>
> Jnotify is developed by someone who has a deep understanding of the
> platform-specific issues.   I do not envy that task.  See the caveats in the
> per-platform notes prominently linked on the jnotify homepage.
>
> I look forward to a day when a standardized cross-platform  solution is
> widely implemented.  Until then, kits like jnotify will help in many
> instances, but probably not without platform-specific pains.  Meanwhile I
> hope very much that Play will continue first-class support for robust
> solutions, even at the expense of efficiency.
>
> Carlos
>
> On Jul 19, 2012 10:51 AM, "Guillaume Bort" <guillaume.b...@gmail.com> wrote:
>>
>> Hi all,
>>
>> We just introduced a new way of detecting file changes in static asset
>> files. It now uses the jnotify API to detect filesystem changes
>> instead of checking the last modified date for each file at each
>> request. I hope that it will fix all issues related to static assets
>> reloading performance in development mode.
>>
>> The commit is in the master:
>>
>>
>> https://github.com/playframework/Play20/commit/e170e85b968e71d5ac0370dd4faec36faa57ad01
>>
>> Please check and comment if it properly fixes your problems.
>>
>> Thanks.
>>
>> --
>> Guillaume Bort, http://guillaume.bort.fr
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "play-framework" group.
>> To post to this group, send email to play-framework@googlegroups.com.
>> To unsubscribe from this group, send email to
>> play-framework+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/play-framework?hl=en.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "play-framework" group.
> To post to this group, send email to play-framework@googlegroups.com.
> To unsubscribe from this group, send email to
> play-framework+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/play-framework?hl=en.



-- 
Guillaume Bort, http://guillaume.bort.fr