> On Nov 16, 2007 9:12 AM, David King <[EMAIL PROTECTED]> wrote:
>>> You can pass the {last_compile_time, Time} option to
>>> erlyweb:compile(), and it will only compile the files that have
>>> changed since that time (for convenience, erlyweb:compile() returns
>>> the Time value after each compilation).
>> Since obviously {auto_compile,true} already retrieves its last
>> compile time from somewhere, can we get a {last_compile_time,auto} or
>> something in a future release?
> That's a good suggestion. I'll do it.
Thanks. Do you have a trac or bugzilla or something somewhere? Can I
get an account on it?
>>> Is {auto_compile, true} slow for you? I haven't noticed its impact.
>>
>> Yes, it at least triples the access time for pages when no files
>> require re-compiling (of course the impact is more when there are
>> files that do need compiling, but that's expected). Roberto mentioned
>> that this could be due to lots of static files, but that's not the
>> case here; I only have one .js and one .css being served in addition
>> to the rendered pages.
>>
>>
>>
>>
>>
>>>
>>> Yariv
>>>
>>> On Nov 15, 2007 6:28 PM, David King <[EMAIL PROTECTED]> wrote:
>>>>
>>>> Compiling with erlyweb:compile(Appdir,...) takes quite some
>>>> time, and
>>>> compiling with {auto_compile,true} makes every request take a
>>>> while,
>>>> so is there some way to get to the "compile all of the changed
>>>> files"
>>>> functionality directly?
>>>>
>>>>>
>>>>
>>>
>>>
>>
>>>
>>
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"erlyweb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
