Re: Null Cache Storage

Wednesday, April 20, 2011, 7:12:21 PM, Fernando Ribeiro wrote:

> Daniel,
>
> You may have found why the code was originally written this way.
> Too bad that switching to this (better) alternative would break
> existing applications. I will write about it for my personal blog, though.

Well, it's not the most flexible API design regarding template-name
resolution and caching, and how I would do it is certainly too
different to be adapted by FM. But, I can still imagine some
improvements without upsetting the logic of FM. Like, the
Configuration could accept a hook where you can handle the getTemplate
calls and so use your own mechanism.

> I will prepare my code for your new release and watch the mailing
> list (and twitter) for the update, allright?
>
> I will initiate another conversation in a separate thread.
>
> Thanks,
>
> On Wed, Apr 20, 2011 at 1:18 PM, Daniel Dekany <[email protected]> wrote:
> Wednesday, April 20, 2011, 4:48:47 PM, Fernando Ribeiro wrote:
>
>> Daniel,
>>
>> I didn't know there was another option for string templates in the
>> library, that may be interesting for many users, will play more with
>> the library and let you know if I need your help there.
>
> You can simply make Template-s from java.io.Reader with the Template
> constructors. The management of such Template objects is completely in
> your hands. Note however templates made this way will not find each
> other by name (because the Configuration doesn't know about them, and
> the call cfg.getTemplate for #include/#import), so the the templates
> that will be #include-d/#import-ed must be stored on the usual way
> (i.e. "in" the Configuration). At the moment at least... things can be
> improved however.
>
>> I didn't mean to rush you to a release, sorry, do you have a
>> timeframe for 2.3.17 already?
>
> No hard timeframe. But most certainly I won't wait with it for more
> than a few weeks now.
>
> --
> Best regards,
>  Daniel Dekany
>
>
> ------------------------------------------------------------------------------
> Benefiting from Server Virtualization: Beyond Initial Workload
> Consolidation -- Increasing the use of server virtualization is a top
> priority.Virtualization can reduce costs, simplify management, and improve
> application availability and disaster protection. Learn more about boosting
> the value of server virtualization.
> http://p.sf.net/sfu/vmware-sfdev2dev
> _______________________________________________
> FreeMarker-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/freemarker-user
>

-- 
Best regards,
 Daniel Dekany


------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev